Conversation
dhardy
left a comment
There was a problem hiding this comment.
Sorry for the delay. Looks fine if it passes CI.
|
Which it doesn't (this is using Rust 1.36.0): |
|
Oh, so Rust used to not support this? Interesting... |
|
I'll investigate later what changed when, etc. Keeping these bounds really is only an issue of documentation after all, so it's not too bad. If we need to keep them, I might change this PR so that comments are added in the source code on these bounds, pointing out they're redundant but used to be needed and are kept for MSRV support. |
|
1.36.0 is 2.5 years old by now; when we asked there was generally little interest in support beyond six months old, so an MSRV bump is not out of the question (even if this is only a minor thing). |
|
The relevant fix in rustc was apparently rust-lang/rust#73905. The code without the extra bound (i.e. the code in this PR) works from Rust |
|
This needs an update to the changelog and a bump to Rust 1.51 (see #1165). |
52a61d9 to
116d75a
Compare
|
Rebased |
There were 3 trait implementations that placed redundant
AsRef/AsMutbounds on<R as BlockRngCore>::Resultswhich were already implied by the bounds in theBlockRngCoretrait definition.Noticed those because they show up in the documentation, e.g. here.
Also fix 2 warnings (one clippy warning, one rustc warning).