Closed NeeEoo closed 3 years ago
Because this change works only for trivial cases where you have in the code
<something> / 0
or
<something> % 0
I think it would be better to stop the compilation and display a proper error message, rather than compiling, running, and then have the runtime division error guaranteed to be executed
Would a warning be better? Or should i make it so that it raises an ZeroDivisionError
Your decision :) I think it should raise an exception (BFSemanticError) and stop
Merged, thank you!
Just wondering did you squash my commits? Since I made 2 commits but there is only 1 listed.
Yes, I did I don't want many commits for one issue :)
Ah okay. Was also confused why it said that my commit was verified with a key, but that key belongs to GitHub so no worries.
Closes #11