-
Notifications
You must be signed in to change notification settings - Fork 385
Use host's rng when communication is enabled #914
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
Conversation
@bors r+ lgtm then |
📌 Commit b44fd97 has been approved by |
Use host's rng when communication is enabled This uses the host's randomness when the communication enabled flag is used. I am not sure about the error handling. I was thinking about fallbacking to `rand` if `getrandom` fails and also print something so the user knows miri is not using the host's rng because it failed. Let me know what you think. Related issue: #800. r? @RalfJung @oli-obk
Also could you expand the |
Sure |
@bors r- retry |
Thanks! @bors r+ |
📌 Commit f53b5b0 has been approved by |
Use host's rng when communication is enabled This uses the host's randomness when the communication enabled flag is used. I am not sure about the error handling. I was thinking about fallbacking to `rand` if `getrandom` fails and also print something so the user knows miri is not using the host's rng because it failed. Let me know what you think. Related issue: #800. r? @RalfJung @oli-obk
☀️ Test successful - checks-travis, status-appveyor |
This uses the host's randomness when the communication enabled flag is used. I am not sure about the error handling. I was thinking about fallbacking to
rand
ifgetrandom
fails and also print something so the user knows miri is not using the host's rng because it failed. Let me know what you think.Related issue: #800.
r? @RalfJung @oli-obk