Closed Sup3rGeo closed 1 year ago
No. This is due to the way lazy evaluation works in Emrichen. There is currently no way to redefine a variable in a way that refers to the previous value of the variable.
The only way I could think of would involve some kind of ”eager” (as opposed to lazy) evaluation operator, something like !
in Haskell. I'm struggling to think of a compelling use case for this, though; most of those I can think of can be worked around by using another variable.
Thanks for the clarification! Using another variable is indeed the way we have been doing so far, which is not a big deal.
Would it be possible to make something like this work without a Max recursion error?
I assume it is because we are referring to
name
in the definition ofname:
incomposed.yaml
, but I would expect that it would use the then already existingJohn
default fromoriginal.yaml
, resulting in "Hi John and Mark"