More panic info on failure of Windows rand#101456
More panic info on failure of Windows rand#101456ChrisDenton wants to merge 1 commit intorust-lang:masterfrom
Conversation
Add the error messages of both `BCryptGenRandom` and `RtlGenRandom` in the (unlikely) event they both fail. Also use an `isize` for the algorithm handle instead of a pointer. This matches the windows-sys crate.
|
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
I think @bors r+ |
|
@bors r- |
|
I'm closing this and replacing with a PR that fixes a problem on WINE. |
…omcc Open a BCrypt algorithm handle Fixes rust-lang#101474, supplants rust-lang#101456. Replaces use of a pseduo handle with manually opening a algorithm handle. Most interesting thing here is the atomics. r? `@thomcc`
Open a BCrypt algorithm handle Fixes rust-lang#101474, supplants rust-lang#101456. Replaces use of a pseduo handle with manually opening a algorithm handle. Most interesting thing here is the atomics. r? `@thomcc`
Add the error messages of both
BCryptGenRandomandRtlGenRandomin the (unlikely) event they both fail. Ideally I'd love to print diagnostic information if onlyBCryptGenRandomfails but that's not really possible here.Also use an
isizefor the algorithm handle instead of a pointer. This matches the windows_sys crate and I think it doesn't make sense to pretend they're pointers when we don't (and won't) use them as such. But I can undo that change if it's a bridge too far.r? @thomcc