Ferrite.jl Having to send a time into the function for constraints is a design failure.

This should just be handled by sending in a closure f(x) = f(x, t, ...).

May 08 '18 08:05 KristofferC

So t should be a global variable then?

May 08 '18 08:05 fredrikekre

No, t can be a local variable and you send in the closure x -> f(x, t). Just like always when you need to pass parameters.

May 08 '18 08:05 KristofferC

But we give the function only once, when creating the condition.

May 08 '18 08:05 fredrikekre

Yeah but you can change t afterward. Perhaps that's what you meant.

May 08 '18 08:05 KristofferC

TIL

May 08 '18 08:05 fredrikekre

Another proposal: Let user define f(x, args...; kwargs...) -> value and then call update!(ch, args...; kwargs...) as appropriate. update! would then splice in the x as f(x, args...; kwargs...).

May 14 '18 12:05 fredrikekre

Maybe a NamedTuple is appropriate? User defines f(x, nt) -> value and call update!(ch, nt).

Sep 05 '18 09:09 fredrikekre

Maybe, but I wonder if not just propagating args...; kwargs... (like you have in the PR I think) is easier in that case.

Sep 05 '18 13:09 KristofferC