Post #3028322
2026-06-01 18:26 UTC
@zwarich@hachyderm.io yeah the source compat issues are what the current swift attempts tend to get wound up in. but having a `yield` statement to evaluate an expression feels kinda gross to me as a half-measure. if you don't need to evolve an existing syntactic structure, evaluating the last expression seems like the better way to go to me
Replies (1)
-
@zwarich@hachyderm.io 2026-06-01 18:30
@joe@f.duriansoftware.com Is there another way to support both relative enum `.constructor(...)` syntax and Swift-style semicolon avoidance while implicitly returning the last expression? That was the main constraint forcing me to have some sort of marker keyword for the last expression.