rust/library/core/src/iter
Dylan DPC 339786e012
Rollup merge of #110958 - compiler-errors:stdlib-refinement, r=cuviper
Make sure that some stdlib method signatures aren't accidental refinements

In the process of implementing https://rust-lang.github.io/rfcs/3245-refined-impls.html, I found a bunch of stdlib implementations that accidentally "refined" their method signatures by dropping  (unnecessary) bounds.

This isn't currently a problem, but may become one if/when method  signature refining is stabilized in the future. Shouldn't hurt to make these signatures a bit more accurate anyways.

NOTE (just to be clear lol): This does not affect behavior at all, since we don't actually take advantage of refined implementations yet!
2023-04-29 11:27:55 +05:30
..
adapters replace version placeholders 2023-04-28 08:47:55 -07:00
sources rm const traits in libcore 2023-04-16 06:49:27 +00:00
traits rm const traits in libcore 2023-04-16 06:49:27 +00:00
mod.rs Bump to latest beta 2023-03-15 08:55:22 -04:00
range.rs Make sure that signatures aren't accidental refinements 2023-04-28 17:36:49 +00:00
sources.rs VecDeque::resize should re-use the buffer in the passed-in element 2022-11-15 00:53:26 -08:00