Use associated_type_bounds where applicable - closes #61738#63350
Use associated_type_bounds where applicable - closes #61738#63350bors merged 3 commits intorust-lang:masterfrom
Conversation
|
r? @KodrAus (rust_highfive has picked a reviewer for you, use r? to override) |
|
r? @Centril |
|
@alexreg I rebased this onto master. Unfortunately the fix for the associated type bounds (#61919) seems to not fully fix the issue (#61752). I still get the following two errors: and both of which do not occur without associated type bounds. |
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
|
Well it certainly does fix #61752, because I added a regression test for that. Can you submit a new issue, minimised, please? |
|
@alexreg I've tried everything, can't reproduce it in a test. It looks like there are multiple factors playing together. I've copied the |
|
@iluuu1994 Have you tried a clean build? No |
|
@alexreg Yes. Note that the build here also fails with the exact same error message. |
|
Not sure then... maybe @Centril can take a look. |
|
@iluuu1994 Let's move out the parts that don't work for now and revisit those parts in a smaller PR after this one has merged. |
8f5ceaa to
3a6a29b
Compare
Centril
left a comment
There was a problem hiding this comment.
Thanks! r=me rollup when green
|
@iluuu1994 Also, can you file an issue for the |
This comment has been minimized.
This comment has been minimized.
|
Bummer, there was a |
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
|
Still missing a feature gate in Let's see if we can work out the issue with the other tests in the next PR, though I'd still be surprised if it's something non-trivial (albeit perhaps not obvious either). |
|
Sorry about that, I really need to buy a more powerful computer so I can rebuild more often. |
a5208c3 to
3d231ac
Compare
|
Oops, I've just noticed that code using the macros in src/libcore/str/mod.rs will fail unless they specify EDIT Maybe not? My local tests failed for that reason but in CI it succeeded. Maybe it was a caching issue. |
|
Seems odd; only one macro is affected in this PR and it does not seem related to the test. @bors r+ |
|
📌 Commit 77bfd7f has been approved by |
No worries, easily done. You may want to check out my post about the GCC Compile Farm on Rust Internals, get an account, and enjoy the faster build times! |
…s, r=Centril Use associated_type_bounds where applicable - closes rust-lang#61738
|
Thanks for the tip, I'll check it out 😊 |
…s, r=Centril Use associated_type_bounds where applicable - closes rust-lang#61738
…s, r=Centril Use associated_type_bounds where applicable - closes rust-lang#61738
…s, r=Centril Use associated_type_bounds where applicable - closes rust-lang#61738
Rollup of 7 pull requests Successful merges: - #63056 (Give built-in macros stable addresses in the standard library) - #63337 (Tweak mismatched types error) - #63350 (Use associated_type_bounds where applicable - closes #61738) - #63394 (Add test for issue 36804) - #63399 (More explicit diagnostic when using a `vec![]` in a pattern) - #63419 (check against more collisions for TypeId of fn pointer) - #63423 (Mention that tuple structs are private if any of their fields are) Failed merges: r? @ghost
|
☔ The latest upstream changes (presumably #63428) made this pull request unmergeable. Please resolve the merge conflicts. |
|
@bors retry r- |
No description provided.