Martin Janiczek
Martin Janiczek
Another option might possibly be having `| Comment Expr` as another Expr *variant*? Unsure. Also I found this article: https://github.com/terrajobst/minsk/blob/master/docs/episode-24.md
> I tried this approach first. It produces code like this: > In contrast, the WithState forked parser module let you do this: I'll have to think about this a...
@pablohirafuji Could you try? :pray: I feel bad asking you to basically duplicate the effort, but I believe it's an important decision so it deserves two spikes in different directions...
We'll likely need to remember all whitespace "inside" expressions One thing that I've learned from today's discussions that I probably should disseminate here (apparently it was a lesson learned the...
Woot woot! I'll take a look at this relatively-soonish :slightly_smiling_face: Thanks @pablohirafuji !
Oooh. This will be interesting. Thanks for finding this out!
For the mathematical operations, I don't expect us to implement Peano arithmetic or something. We can keep the `type Int = Int` and overwrite stuff in the compiler, like the...
Ideally we'd allow usage of the packages (download them and all) but have our overrides for each platform (as much Elm-only as possible to minimize the amount of non-Elm overrides...
Link to some further discussion on Discord: https://ptb.discordapp.com/channels/578305644780716039/578305645824966669/602182350352285717
@j340m3 Doesn't making `&&` a normal function mean that you need to evaluate both arguments before passing them into that function? ie. shortcircuiting would not be there anymore?