hvega
hvega copied to clipboard
Do we follow the Elm API or branch off into Haskell land?
So, should this module follow the Elm API (which means solving #1), or take advantage of Haskell-only features? I currently don't have any ideas about what could be changed, as I think that would come from actually using the API in real-world cases.
Hi there! First of all, thank you for this library, it was really lovely to find out that this exists.
To add to your question above:
- Which Haskell-only features could you leverage right now?
- Do actually you see any potential issues with elm-only features like anonymous/extensible records?