Kristoffer Carlsson
Kristoffer Carlsson
Fixes https://github.com/KristofferC/OhMyREPL.jl/issues/267
JuliaSyntax.jl is the future of Julia parsing in Julia so it makes sense to start using that over Tokenize.jl that will likely be deprecated.
 Linter message is "Invalid redefinition of constant." That seems weird to me.
RGB colors have very spotty support in terminals so probably better to use something more well-supported. `Base.error_color()` is by default `:light_red` but can also be customized with an env var....
This makes "untokenization" slightly more annoying (since you need to look at the previous token to know where to start) but I think it is worth it. Some tests needed...
See https://github.com/JuliaLang/julia/pull/47040
Happened to see this: https://github.com/JuliaLang/Pkg.jl/blob/ca9f4426568d85d2ed276b4ab3083dc8f2184478/src/REPLMode/REPLMode.jl#L296-L309 This is not great, it adds a constructor to a certain type of dictionary. This should likely just be its own type.
https://github.com/JuliaLang/Pkg.jl/actions/runs/3157873266/jobs/5139255214 ``` Artifacts.toml Utilities: Test Failed at /home/runner/work/Pkg.jl/Pkg.jl/test/artifacts.jl:237 Expression: artifact_hash("foo_txt", artifacts_toml) == hash2 Evaluated: SHA1("5679c650921bf0f891224295dd95572a5e9db8da") == SHA1("09795a47b3e5d3bcc4b44beace0072e1c3eb8aab") ``` Not sure what changed.
It looks like it is completely undocumented.
I didn't really like the > If a manifest file exists and the `allow_reresolve` keyword argument is set to `false`, the versions in the manifest file are used. Otherwise a...