Auke Booij
Auke Booij
I worked on this for a while but hit a few bumps. I sent a [message](https://mail.haskell.org/pipermail/haskell-cafe/2017-January/125888.html) to the haskell-cafe mailing list. So no real progress on this issue yet, but...
Okay, since 3eab352 we can read XML data into a protocol object and process it into another object which can be used to track which wayland ID has which ....
(TODO: reduce code duplication by parameterising whether the particular protocol flavor has the cross-references as `String`s or as actual `Interface`s/`ArgEnum`s. This will need type fixpoints, as in [Sergey](https://mail.haskell.org/pipermail/haskell-cafe/2017-January/125891.html)'s response to...
(This TODO is now implemented by 72279ed.)
I've started trying to write some client code that interfaces with a compositor in a rather "raw" form. ```haskell main :: IO () main = do s die "Couldn't parse...
Over the past few months I've tried to think of an ideal haskell API. One thing that has been bugging me is that we can't "pass around" references to arbitrary...
So more concretely, and at the same time more vaguely: in Haskell language, what is a stateful communication protocol?
One possible definition is to say that the wayland state and the user code's state are both state transition systems. Then to say that the states cohere means something like...
Also, [this](http://reasonablypolymorphic.com//blog/type-directed-code-generation) is a really nice approach to making everything type safe.
I will also read [this](https://ren.zone/articles/opaleye-sot) and then write a proof of concept.