Re:A quick introduction to data parallelism in Julia
by nextos on Tuesday October 06, 2020 @07:58PM
(#24703884)
Yes, I agree getting design choices right is important in order not to end up with a lot of legacy code in future versions of Julia.
I think the pipe operator is probably the area that needs most urgent attention. Lots of libraries have their own slightly different macros for improved pipes with partial application, and that introduces a bit of fragmentation and hurts composability.
There's an open issue for this with some background: https://github.com/JuliaLang/julia/issues/5571
Since Julia is committed to semantic versioning, this is a kinda scary prospect because it means that any high level, exported interface we decide on, we'll be stuck with until at least 2.0 and probably forever.
So with things like this, it's important to be conservative about the interfaces we expose and instead, we've have people explore different approaches out in the package ecosystem. One day, if someone can make a strong enough argument, I'm sure we'll see one of these package solutions end up in Base.