> had 0 problems with Revise
Try changing a struct.
Yes, that is an important limitation of Revise that I hope goes away.
Until then, consider this work-around: https://github.com/BeastyBlacksmith/ProtoStructs.jl
That's definitely a problem. I work around by naming all my structs with a `_1` suffix and `%s/_1/_2/g` (VIM find-replacing) every time a struct changes. Otherwise I find Revise works great.
Re:Julia 1.6 addresses latency issues
by fishmaster on Wednesday May 26, 2021 @09:29AM
(#27290231)
Wrap it in a module, then you can change it without any problems. It's not ideal, but it works very well in practice.
Revise can’t change structs in modules either. The only sane way I’ve found to handle this is using a Pluto notebook. But that’s not for everybody.
Re:Julia 1.6 addresses latency issues
by fishmaster on Thursday May 27, 2021 @02:40PM
(#27306531)
I can definitely redefine a struct in a module.
1) I use VScode and have had 0 problems with Revise. It Just Works when using the Julia extension + built in REPL. I actually prefer the Julia environment to Python in VScode, I have way fewer problems when doing a Notebook-like workflow where I’m writing library code at the same time
2) Agreed, I also wish there was a better story here. I’m constantly frustrated by how little static support there is. It’s getting better though, eg precompilation in 1.6.
3) I haven’t had any issues here outside of the occasional update to VScode Julia extension that botches things
4) I’ve had quite a lot of luck on discourse and GitHub issues, as well as slack for the occasional small question
Rust is great for use cases where you have specific resource management needs, although seems an odd choice for general purpose scientific computing.