3 ms·
The first point has been on the radar for quite a while (i.e. years), but it's really non-trivial, and not at all necessary for the core language (hence not a p
by dbaupp 11y ago
The first point has been on the radar for quite a while (i.e. years), but it's really non-trivial, and not at all necessary for the core language (hence not a priority for stability) since it's basically just some syntactic niceties over existing functionality.
- acconsta 11y ago> it's basically just some syntactic niceties over existing functionality. OK, cool! Can you point us to the existing functionality, or any example of it being used for stackless coroutines?
- dbaupp 11y agoEnums. This HN submission is an example.
- acconsta 11y agoState machines aren't a general solution — you have to write a state machine by hand for every application. Stackless coroutines are — the compiler (or a clever library) transforms your ordinary function into a state machine.
- dbaupp 11y agoYes, I know. That's exactly what I mean by syntactic sugar: it is an automated way to write something that could already be written, but is annoying to do by hand.
- acconsta 11y agoOh, OK. When I hear syntactic sugar, I think of like a macro. Thanks though, I'm glad this is on the core team's radar.