This line of code creates a 1000 element array of values, evenly spaced from 0 to 10: x = range(0,10,length=1000) The code above works perfectly. This line of code, however, throws an error: x = range(0,10,length=1e3) As I understand it, 1000 should be the same thing as 1e3, and I’ve checked to …

I think you’re arguing here for a “do what I mean” behavior. Floating point “integers” like 1e10 usually don’t match their closest integers perfectly, but there’s rounding error involved. So saying something like “9.9999999” is 10 just because it’s very close to 10 invites a lot of bugs and weird be…

[image] chadagreene: To me, the fact that Julia breaks with 1e3 but not 1000 feels like a small and unnecessary step backward from MATLAB. In general, Julia is actually very accommodating when it comes to accepting varying input types. Much more so than Matlab. When calling built-in Matlab fu…

The error thrown by Julia is actually pretty good in this case, and almost the same as Python gives: julia> range(0, 1, length=1e2) ERROR: TypeError: in keyword argument length, expected Union{Nothing, Integer}, got a value of type Float64 Stacktrace: [1] top-level scope @ REPL[1]:1 vs In [1]…

[image] aplavin: but 1e20 != 10^20 . Unfortunate example since the left hand side can be represented exactly but the right hand side overflows. julia> 1e20 == BigInt(10)^20 true julia> 10^20 7766279631452241920

Indeed, you are right! A better example would probably be Int(1e16 + 1) == Int(1e16) which would make range(... length=1e16 + 1) very confusing.

I’m wrong about the syntax being free, currently 1E6 === 1e6. So this would be a breaking change for a small gain. Ignore.

Good catch. That’ll be fixed by https://github.com/julia-vscode/julia-vscode/pull/2862

[image] jules: Floating point “integers” like 1e10 usually don’t match their closest integers perfectly, but there’s rounding error involved. Actually, they “usually” do match: Float64 floating-point numbers represent all integers exactly up to maxintfloat(Float64) = 2^53, about 10^16. Moreo…

I think we should make an exception here, for pragmatic reasons. My argument is that, despite what you write floats representing “many integers” exactly (well because), but not all, and length an integer (counted, never measured), I realized no float for length would be problematic: julia> range(0…

Rather than upend the entire language, you can myrange(start,stop,len) = range(start,stop,length=Int(len)) julia> myrange(0,10,1e3) 0.0:0.01001001001001001:10.0

Why does scientific notation break the range function?

New to Julia

Topic		Replies	Views
A most harrowing collection of Julia WATs General Usage wat	108	12829	January 27, 2024
Range(stop) Internals & Design range	17	3017	January 22, 2021
Type restriction on UnitRange Internals & Design question	17	1635	October 21, 2017
Syntax Surprises General Usage syntax , discussion , fun , gotchas	83	6353	January 21, 2023
UndefVarError: linspace not defined New to Julia	40	41574	July 30, 2020

Why does scientific notation break the range function?

Related topics