Both of those are small potatoes and don’t actually give new things. SimpleTraits.jl and Parameters.jl cover those quite well.
The only things I care for are things I can’t do myself in a package. There are a few rough edges that still need to be sanded down. These are:
- True dispatch from keyword arguments: #16580
- Stack-allocated views: #12205
- Higher bar for or ability to “turn off” splat and recursion penalties:
- Compiler optimizations for small unions.
- The closure performance bug #15276
- Fix up the Julia builds in standard repositories so people stop accidentally downloading Julia v0.4 (mostly a teaching thing).
And the things in the package ecosystem to make it really feel complete:
- GR’s new GUI
- Slow first-time-to-plot on Plots.jl and Gadfly.jl (credit to @musm for mentioning it)
- The current working branches of GPUArrays.jl to merge
- Better testing of packages with binaries on Windows… pretty much all around
- NLsolve.jl to do its “input swap” release
- DataFrames/DataTables/DataUtils/IterableTables/IndexedTables/DataIKEA needs to work itself out (see compiler optimizations for small unions). I am honestly lost here.
- The basic PDE tooling (FDM and Fenics wrappers) needs to be released
- Fix some layout issues in Plots.jl
That’s probably a list of everything that, in the current state of Julia, come up enough that giving a workshop I would expect to have to mention that “it’s a current problem but should be fixed in the near future”. Honestly, none of this is breaking or devastating, or “definitely need to be in 1.0”, but I think Julia will still feel somewhat “new” to me until these kinds of things are completed.
When I look at this list, none of it is really “required” for v1.0. It’s really just optimizations and polish. Necessary polish, but nothing breaking. I think we’re pretty ready.