Rafael Schouten

Oof yes that's ugly. Lets wrap that. It will need some tweaks to work with ConstructionBase.jl (an embarrassing omission on my part) but you should just be able to do...

Yeah that's what I mean... it should but doesn't. We can make it work by definining `ConstructionBase.constructorof` correctly for `Param`.

@lazarusA I'm still thinking about how best to update parameters by number as well as type here, I think we may as well have both?

Works for me? You need to do: ```julia m = @set m.a.val = 2 ``` Or use `@set!` with a bang, which does the reassignment automatically. Setifield.jl returns a new...

immutable is almost always faster

`Param` only has one field, that contains a `NamedTuple` ? That redundancy is common to all inheritance in julia. The additional constructors that do all the work can be generalised...

We already use a method for `parent`, and I wouldnt call that one field "structure". Its one step above a singleton. I get your gripe, bit it really is minor....

I've just been considering swapping DimensionalData.jl over to that too. I wasn't really aware of the package previously. But the problem with defaults provided by packages is we have to...

I always try not to add a dependency... They add up in compile time and CI run time, and it adds maintenance burden. Also thinking about this, doesn't Optim.jl take...

I think you're right about sliders and sets, not including zero is often very useful. But using intervals is definitely more complicated than `Tuple`... If you want to take that...