Brent Yorgey

Edited to add: it turns out that it works (i.e. both print 1) if we switch the order of the strategies `CS.Field "r" ()` and `CR.ReadStatePure` in the derivation of...

Ah, I get it now, thanks for the explanation! I suggest... a big fat warning attached to the `Field` combinator? Or the `ReadStatePure` combinator? Or both? I wonder if there...

Latest thoughts on syntax: instead of having different keywords `infix`, `prefix`, etc., let's just have one keyword `operator`, with fixity specified by `~` characters. And instead of `same precedence as`...

We also need to be able to parse operator *definitions*. Or perhaps we just require that an operator has to be declared to be a synonym for some named function....

See the `user-ops` branch: https://github.com/disco-lang/disco/tree/user-ops . Next steps: - [x] finish `parseOpDecl` - [ ] Edit `parseStandaloneOp` to parse *any* standalone-op-like thing instead of only those that are built in....

Once we have `Prop` (#217) and the ability to specify qualified polymorphic types (#179) we can put these in a library.

Critical since we really need these in order for containers to work properly.

Meh, downgrading to 'moderate' importance. From a theoretical point of view, yes, this is important to get `reduce` to behave correctly. But at this point it's not something students will...

Another possibility would be to just have these as built in primitives; but I don't like that because I want students to know the definition of these properties, and being...

Actually, should be easy now with the enumeration library!