Consider using ragel to generate state machine for wlc

[Cloudef]

wlc's main job is mainly abstracting away various backends and APIs (x11, drm, libinput, udev, etc...), but it also has lots of manual code for state (when view should be drawn, what is the state of view, when to commit, damages, etc...) which could probably be abstracted as a state machine.

I'm not yet sure how this idea would work, but if ragel is up to the task, all the "moving parts" in wlc are easily graphed and generated, and debugging is easier. It also would increase reliability, that is, wlc works as described in state machine.

[Cloudef]

Related issues:
Cloudef/orbment#106
Cloudef/orbment#114
Cloudef/orbment#109
Cloudef/orbment#108
Cloudef/orbment#102
Cloudef/orbment#104
Cloudef/orbment#98
Cloudef/orbment#93
Cloudef/orbment#92

[Cloudef]

This would decrease test coverage area a lot as well.

[Cloudef]

My local prototyping seemed promising. Going to start experimenting with this on ragel-fsm branch.

[Cloudef]

This may be worth doing for wlc2 if that ever happens (being API compatible with wlc though)