I only had time to glance at the README but there’s much resonance. The York Lava that Reduceron uses, uses the Haskell typing system to, but it’s so forced that it become IMO a bigger burden of its own. I’m not a purist and that’s (probably going out) 1/2
Conversation
I loved the sequential model of Handel C, rather `;` being the clock edge, I wanted it explict. FpgaC and host of other languages does it too (something calling `yield`). Anyway I don’t usual share things this half baked, but I’ll push my POC soon 2/2
1
Cool. I'm curious. I think I've learned enough with my own doodling that I can take in new ideas. And about not publishing half baked ideas: just don't write docs, everyone will ignore :)
1
1
Maybe it would be interesting to create a survey of ideas and see how these projects are subtly different in goals and implementation. There are a lot of approaches. I feel my goal is mostly towards a simple macro language, to not get lost in unbounded Haskell cleverness.
2
1
My goal would be a language in which straight forward logic looks ... straightforward. A more lofty and conflicting goal (maybe a different language) would would be one where you cannot so easily mix different time domains. Perhaps some CSP-like model (yes, Handel-C did it)
1
CSP is definitely high on my list. I started structuring code that runs in the same clock domain like this as well. For the rest I just want good composition, and substrate abstraction, e.g. run the same filter code in parallel, bit-serial, or sequential on CPU.
1
Papers have some nice insights too. Too bad I have to stay on task after recent procrastination run but I wonder how much work it is to implement this as a Haskell DSL (e.g. on top of Ivory), a Rust macro.