@reactive! not working on Julia 1.8
See original GitHub issuejulia> @reactive! mutable struct Example1 <: ReactiveModel end
ERROR: setfield!: const field .name of type TypeName cannot be changed
Stacktrace:
[1] setproperty!(x::Core.TypeName, f::Symbol, v::Symbol)
@ Base ./Base.jl:39
[2] top-level scope
@ ~/.julia/packages/Stipple/ikRxD/src/Stipple.jl:1291
If it can not be fixed, I suggest removing the feature. @hhaensel
Issue Analytics
- State:
- Created a year ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Problem with precompiling Plots in Julia 1.8.2
Hello I have problems using Plots after installing. Julia 1.8.2, precompiling does not work, how to solve this problem ? Thanks a lot....
Read more >biaslab/ReactiveMP.jl: High-performance reactive ... - GitHub
ReactiveMP.jl is a Julia package that provides an efficient reactive message passing based Bayesian inference engine on a factor graph.
Read more >Docstrings · Pluto.jl - JuliaHub
Tries to add information about macro calls without running any code, using knowledge about common macros. So, the resulting reactive nodes may ...
Read more >Introduction - Reactive.jl
Reactive.jl is a Julia package for Reactive Programming. It makes writing event-driven programs simple. Reactive borrows its vocabulary from ...
Read more >First Steps #1: Installing Julia - Julia For Data Science
Double-click the .dmg file and drag "Julia-1.8" into "Applications". ... If you run into a package that doesn't work on your M-series ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Not nice means, the name of the type is not the original one, but we assign a variable with the correct name with that strangely named struct. When you call it, you see that the name is different.
Well, I fixed this already 4 days ago 😉