And even if you're in a REPL you're out of luck since you cannot reload maybe kinds of code changes without restarting the REPL. Revise.jl is supposed to solve this problem, but last time I tried writing a Julia project (v1.6), I ran into a lot of issues.
Eventually I abandoned Julia because while in theory it seemed like a very nice language, in practice I ran into so many issues that I began to wonder if the core devs even use their own product at all.
I think you’re probably referring to how redefining a struct breaks Revise.jl and you have to restart the REPL? There are some other rough edges but IME this is the most noticeable
You can use Pluto.jl for this kind of rapid prototyping where you might want to change your structs a lot. It works pretty well with Revise, so when you get things the way you like it can move that struct definition out into your package code.
The other common suggestion is to prototype with NamedTuples instead of structs
Comments
And even if you're in a REPL you're out of luck since you cannot reload maybe kinds of code changes without restarting the REPL. Revise.jl is supposed to solve this problem, but last time I tried writing a Julia project (v1.6), I ran into a lot of issues.
Eventually I abandoned Julia because while in theory it seemed like a very nice language, in practice I ran into so many issues that I began to wonder if the core devs even use their own product at all.
I think you’re probably referring to how redefining a struct breaks Revise.jl and you have to restart the REPL? There are some other rough edges but IME this is the most noticeable
You can use Pluto.jl for this kind of rapid prototyping where you might want to change your structs a lot. It works pretty well with Revise, so when you get things the way you like it can move that struct definition out into your package code.
The other common suggestion is to prototype with NamedTuples instead of structs