@HWoidt : you said something that there might be a better way to define process constructors in terms of generating them. As you know, I define the constructors statically (comb12, mealy41, etc.), due to Haskell's strict type system, although they all have recursive definitions. Is there a method that would spare me of this huge amount of boilerplate? I prefer to avoid TemplateHaskell for now, but even if this is not possible, could we have a brainstorming session or could you point me to some documentation that might shed some light upon this matter? Are there any ideas in type-level that I can borrow?
For now it is a low-priority issue and might be completely dropped in the future. The "proof-of-concept" nature of the library suffices with statically-assigned constructors.
@HWoidt : you said something that there might be a better way to define process constructors in terms of generating them. As you know, I define the constructors statically (comb12, mealy41, etc.), due to Haskell's strict type system, although they all have recursive definitions. Is there a method that would spare me of this huge amount of boilerplate? I prefer to avoid TemplateHaskell for now, but even if this is not possible, could we have a brainstorming session or could you point me to some documentation that might shed some light upon this matter? Are there any ideas in type-level that I can borrow?