-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix range check for ChuckSomeDice() #42
base: master
Are you sure you want to change the base?
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/zackradisic/aussieplusplus/5PXUsgyiMpB5WS3Jc5EiyYuJLdq4 |
Hm, the preview still has the error. I'm not quite sure what's going on. |
What's weird is it works locally on my machine. I'm completely new to Rust, so I have no idea how to diagnose the discrepancy. |
Yeah I won’t be able to figure out the difference. I’m hopeful it’s just something wrong with the preview. |
I was able to run this change on my local machine and can see that changing from > to >= works correctly in making sure the proper error message is printed if the range is 0,0! |
actually, I know what the issue is, @bbrk24 |
Huh. I figured such a step would be done automatically or wouldn't touch checked-in files. I tried it just now, locally, and I got this linker error:
I'm not entirely sure why a cmd error came up when I'm using bash, and the solutions I'm finding online don't seem to work either. |
emcc is the webassembly compiler |
from there, when you run |
Fixes #41
It turns out the error wasn't about floats per se --
ChuckSomeDice(0, 0)
would cause the same panic, whileChuckSomeDice(0, 1.5)
wouldn't.