Coding 2023-09-20
I've written a bunch of Impliciula code. It's not ready to show off yet, but it is making me question whether the whole "make code more like sentences than mathematical notation" concept is actually feasible. Some of these lines are over 100 characters, so one thing I need to salvage this is some idea of where line breaks are workable from a parsing perspective, and helpful from a punctuation perspective. I just tried something that looks helpful, but it's still all a little breathless.
Syntax aside, something occurred to me about semantics:
If I keep up the whole gradual typing idea, then code that isn't being accelerated should need to specify the resume behavior of effects at definition time. I think. Like, yes, when the code is being accelerated, it's helpful to guarantee that the fastest/smallest paths allowable get baked in, but in the dynamic regime, the handlers need to be tracked dynamically, so...
Maybe the way to do this is to just allow using _ when specifying what kind of resume behavior an effect has...
In any case, I guess I should focus on the effect syntax, because once I have a version of that that I'm comfortable with, I can put out some more concrete stuff here and elsewhere.
Anyway, I should stop looking at my screen.
Good night.