Carl Mäsak
Carl Mäsak
Since unquotes are no longer made of stuff but are holes (#334), I'm left wondering how to go about creating them programmatically. (Manually is easy; just use the unquote syntax.)...
> I _think_ it'd be OK and not breaking the SER to take the `location` of the same unquoted expression several times... but, to be honest, I'm not sure. It's...
@vendethiel cf. #234. 😉
I just slapped the `currently-needs-more-design` label on this issue, because I would like for it to be spelled out in a small spec how the code generation handles control flow...
Bumping this because @vendethiel and I started a skunkworks implementation of the `is succinct` processor yesterday. Hoping to be able to put up a PR with it later today. The...
Uhm, `last(...)` is unfortunate if we ever go with `last` as a control flow keyword. How about `old(...)`, similar to how Eiffel does it?
> - Not run any statement with `last(...)` in it if it's the first iteration. This might be a bit extreme. But how about: - Either `last(category)` turns into `None`...
Agreed. I could live with either `prev` or `previous`, actually.
Came in here to suggest `old(...)`, but noticed I was four years too late.
And besides, I think I actually like `prev` better. Even though it's in quite a different category, it has a nice Strange Consistency with `next`.