▲ | eviks 8 days ago | |
Unless workarounds to a missing feature have a higher maintenance burden like in this case, and you can't avoid it via learning | ||
▲ | mjevans 8 days ago | parent [-] | |
Go's preferred way would probably be something like compute the aliased operations on the line(s) before, then reference the final values. E.G. Adapting https://github.com/golang/go/issues/34174
The inline {variable} reference suffix format would be less confusing for situations that involve _many_ variables. Though I'm a bit more partial to this syntax with an immediately trailing %{variable} packet since my gut feeling is that special case would be cleaner in a parser.
|