Kristoffer Carlsson

This seems like a strange place to put basic information on how to store objects to variables or how to index arrays etc. But also see https://github.com/JuliaLang/julia/pull/38791. ``` julia> ?("foo",...

Maybe run a PkgEval and merge if it looks ok?

Or just merge, tests pass after all and I guess we will find it in release PkgEval if it is too bad

You can open a PR with that as a commit against this branch or just post a commit SHA and I will push it here.

@nanosoldier `runtests(["FHIRClient", "Flamenco", "GAP", "HydrophoneCalibrations", "SwagUI"], vs = ":release-1.8", configuration = (buildflags = ["LLVM_ASSERTIONS=1", "FORCE_ASSERTIONS=1"],), vs_configuration = (buildflags = ["LLVM_ASSERTIONS=1", "FORCE_ASSERTIONS=1"],))`

@nanosoldier `runtests(["ArgoData", "BayesianQuadrature", "Flamenco", "FluxTraining", "GeometryPrimitives", "HydrophoneCalibrations", "OceanBasins", "OptimKit", "RainFARM", "SimpleFWA"], vs = ":release-1.8", configuration = (buildflags = ["LLVM_ASSERTIONS=1", "FORCE_ASSERTIONS=1"],), vs_configuration = (buildflags = ["LLVM_ASSERTIONS=1", "FORCE_ASSERTIONS=1"],))`

I mean, 33% of it has nothing to do with Pkg heh ``` [19] eval_user_input(ast::Any, backend::REPL.REPLBackend, mod::Module) @ REPL /data/vtjnash/julia/usr/share/julia/stdlib/v1.9/REPL/src/REPL.jl:147 [20] repl_backend_loop(backend::REPL.REPLBackend, get_module::Function) @ REPL /data/vtjnash/julia/usr/share/julia/stdlib/v1.9/REPL/src/REPL.jl:248 [21] start_repl_backend(backend::REPL.REPLBackend, consumer::Any; get_module::Function)...

Yes, that's the idea.

I think this is a good idea but it feels a bit "spammy" to print it for e.g. normal arrays. Maybe it should only be printed when the axis is...

We could add more details of the type of formats we accept in `parse`. For example: ``` julia> parse(Float64, "0x2.3ep5") 71.75 julia> parse(Int, "0o777") 511 ``` but just adding a...