diff options
| author | Dylan DPC <99973273+Dylan-DPC@users.noreply.github.com> | 2023-04-29 11:27:55 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-04-29 11:27:55 +0530 |
| commit | 339786e01203f0ea00601b605899429c2b4bdf3e (patch) | |
| tree | a6e9301322075c6407f405e51e0141732ab2eb2d /tests/rustdoc-js-std/parser-errors.js | |
| parent | 650f8fddd9ba3eb2127879a7aed04bbeb4b8045d (diff) | |
| parent | 33871c97ab67d90cfca5c22183f3a4e200d6a976 (diff) | |
| download | rust-339786e01203f0ea00601b605899429c2b4bdf3e.tar.gz | |
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!
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions