Hi all, first time posting. Apologies anywhere my understanding is off, and please forgive that I am not a great communicator in this domain. I’ve nonetheless invested some time to write the most careful and concise observation I can. Looking over PR #25896 and subsequently #28708 , the latter pro…

I’m trying to find the call to action here. Can you boil this down a bit? If you have an improvement in mind for the documentation, the best way to get it reviewed is to submit a PR to the source . If I understand #28708 correctly, the option left open for the future is making the two-positional-a…

[image] jne: I suppose you mean that clarity is negatively related to how many non-keyword arguments there are, each of which is intelligible only through positional inference Yes; I don’t think we should have range(a,b,c) because it’s too hard to guess what the arguments mean. Making it wors…

range(stop=100) could even return a OneTo for efficiency.

[image] jeff.bezanson: Yes; I don’t think we should have range(a,b,c) because it’s too hard to guess what the arguments mean. Making it worse is that we have a:b:c where the order is start,step,stop, so range(a,b,c) using the order start,stop,length would be very confusing IMO. I suspect most…

You can already get this behavior via LinRange: julia> LinRange(1, 2, 5) 5-element LinRange{Float64}: 1.0,1.25,1.5,1.75,2.0 It’d be nice to have a two-argument constructor with a default length of 100 for interactive use: julia> LinRange(0, π) 100-element LinRange{Float64}: 0.0,0.0317333,0.0634…

[image] stillyslalom: You can already get this behavior via LinRange : I did not know that, thanks!

[image] antoine-levitt: allow range(a,b,length) in practice Many books on coding style discourage 3+ positional arguments because they are difficult to remember, require a lookup in the documentation, and thus can mask bugs. Base and the standard libraries have been moving in this direction …

Yes, there has been a global push towards keyword arguments in julia 1.0. This has been great for consistency, but the likes of range(0,stop=1,length=100) and dropdims(sum(a,dims=1),dims=1) are not that nice to write or read. There is a tension between usability/concision and consistency/purity (th…

[image] antoine-levitt: range(0,stop=1,length=100) […] not that nice to write or read. Perhaps you missed allow `range(start, stop; ...)` JuliaLang:master ← JuliaLang:jb/2argrange opened 08:0…

There is a tension between usability/concision and consistency/purity (think matlab vs scheme); I feel that the balance has shifted towards the latter in several decisions, as Julia distances itself from being a language for technical computing. I think (and hope) this shift is also largely due t…

the `range` improvement for 1.1

Internals & Design

Topic		Replies	Views
Range(stop) Internals & Design range	17	3014	January 22, 2021
Using step in the range function New to Julia question	1	133	November 20, 2025
Start, step, length for `range` Internals & Design	4	5841	March 4, 2021
Why does scientific notation break the range function? New to Julia	95	4566	April 29, 2022
Type restriction on UnitRange Internals & Design question	17	1633	October 21, 2017

the `range` improvement for 1.1

Related topics