Jeff Bezanson
Jeff Bezanson
This also seems unexpected: ``` f() = 1 f() = 2 julia> methods(f, Tuple{}) # 1 method for generic function "f" from Main: [1] f() @ REPL[15]:1 julia> methods(f, Tuple{Vararg{Any}})...
TOML would be good, we just don't yet have a parser available at this stage. It will be awkward, since we don't even have arrays or dicts at this stage....
OK I have a better implementation: - Core.Compiler and Base each have their own settings, since they are separate libraries. You can pass `--settings` to either. - In the process,...
Decided to call this "buildsettings" to clarify they are build-time.
`showall` ? :trollface: Maybe we should try to add some simple line break logic?
> > Maybe we should try to add some simple line break logic? > > What do you mean? Making the entries line up better.
I believe the new method in question is here: https://github.com/JuliaLang/julia/blob/45a0381baf5555952caea0ccb43b377ac5ec8ae2/stdlib/LinearAlgebra/src/generic.jl#L247 I would just go ahead and submit a draft PR; then folks who tend to review LinearAlgebra will comment.
This needs a different name. We use "undef" to mean a null reference. Maybe just `FieldError` or `PropertyError`?
We have been through a couple implementations of this function and it has been risky to touch it in the past. This needs more motivation; what is the big benefit...
Triage thinks this is too breaking. We could potentially do something else with bigfloat precision like using a ScopedValue for it, though.