rust/library/alloc
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
..
benches remove some unneeded imports 2023-04-12 19:27:18 +02:00
src Rollup merge of #110958 - compiler-errors:stdlib-refinement, r=cuviper 2023-04-29 11:27:55 +05:30
tests Rollup merge of #110419 - jsoref:spelling-library, r=jyn514 2023-04-26 18:51:41 +02:00
Cargo.toml Revert "Report allocation errors as panics" 2023-04-25 00:08:37 +02:00