Comment by benreesman a day ago
i'm relatively confident that andrew will happily break the language again (god love him for that) when it becomes clear that you really want that algebra.
though i will say, for a systems language, it's probably better to invert the lift/unlift relationship, default to do-notation and explicitly unlift into pure functions. that's almost what const meant in C++ to begin with but it lost it's way.
you're just spreading FUD about zig breaking before 1.0. there is zero basis for you to be "relatively confident" about this matter, because
1. the io situation is basically restructuring analgously to the allocator situation, which is at this point battle tested. there are currently no "monads wrapping statefulness" anywhere in zig.
2. It's not in zig's nature to build something because it it satisifies an fp idiom. the abstractions and resulting "thing that the hardware does" (at least in release builds) are generally more or less obvious. the levels of compiler reinterpretation to achieve functional purity are not really the sort of thing that zig does. for example, zig does not have a privileged "iterator" method that the compiler reinterprets in a way that unrolls blocks or lambdas into loops without crossing a frame boundary.
The same Andrew who rejected even basic interfaces in favour of duck-typed generics or manually written vtables?