Kristoffer Carlsson
Kristoffer Carlsson
Makes sense. Should be fairly easy for someone with the desire to add this
https://github.com/JuliaLang/julia/pull/38791 is related.
> We guess the issue could be addressed in Pkg if extensions would be resolved based on UUIDs instead of names That should already be the case. I'll try see...
I tried this: ```julia pkg> activate --temp Activating new project at `/tmp/jl_SWjSGu` (jl_SWjSGu) pkg> dev . Resolving package versions... Updating `/tmp/jl_SWjSGu/Project.toml` [97c6e3c7] + ExtensionsConflict v0.1.0 `../../home/kc/JuliaTests/ExtensionsConflict` Updating `/tmp/jl_SWjSGu/Manifest.toml` (jl_SWjSGu) pkg>...
Seems like a fairly easy fix. Maybe you want to take a stab at it?
How would that work when changing structs is not supported?
No, invalidating as in having to recompile some Revise functions after CUDA is loaded.
Enzyme invalidation is tracked at https://github.com/EnzymeAD/Enzyme.jl/issues/776
Regarding a FAQ, I remember reading https://gds.blog.gov.uk/2013/07/25/faqs-why-we-dont-have-them/
In my opinion, if you want to reliably serialize/deserialize arbitrary Julia object then the best is to - record Julia version - record package versions (with a manifest) - use...