Uh oh!
There was an error while loading. Please reload this page.
Specialization is unsound - #71420
Conversation
rust-highfive
commented
Apr 22, 2020
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Turns out |
matthewjasper
commented
Apr 22, 2020
They probably should, but I don't know how feasible it is. Once stage0 has |
rust-highfive
commented
Apr 22, 2020
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 |
RalfJung
commented
Apr 22, 2020
That shouldn't be too long. :D I am going to wait for some more feedback on this PR before trying to get the build through. |
This comment has been minimized.
This comment has been minimized.
RalfJung
commented
Apr 24, 2020
This is a rather conflict-heavy PR, would be good if I got quick feedback on this. |
5862fe3 to
2539397Compare
This comment has been minimized.
This comment has been minimized.
RalfJung
commented
May 1, 2020
@matthewjasper stage 0 has |
…ochenkov Incomplete features can also be unsound Some incomplete features do not just ICE, they are also currently unsound (e.g. rust-lang#72029, and also `specialization` -- which is not yet marked incomplete but [should be](rust-lang#71420)). This makes the message reflect that. While at it I also added a link to the tracking issue, which hopefully should explain what is incomplete/unsound about the feature.
…ochenkov Incomplete features can also be unsound Some incomplete features do not just ICE, they are also currently unsound (e.g. rust-lang#72029, and also `specialization` -- which is not yet marked incomplete but [should be](rust-lang#71420)). This makes the message reflect that. While at it I also added a link to the tracking issue, which hopefully should explain what is incomplete/unsound about the feature.
…ochenkov Incomplete features can also be unsound Some incomplete features do not just ICE, they are also currently unsound (e.g. rust-lang#72029, and also `specialization` -- which is not yet marked incomplete but [should be](rust-lang#71420)). This makes the message reflect that. While at it I also added a link to the tracking issue, which hopefully should explain what is incomplete/unsound about the feature.
This comment has been minimized.
This comment has been minimized.
2539397 to
42d4e4bCompareRalfJung
commented
May 17, 2020
Rebased across my other PR which changes the message to include unsoundness. @matthewjasper should I just add |
rust-highfive
commented
May 17, 2020
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 |
RalfJung
commented
May 18, 2020
… r=matthewjasper Specialization is unsound As discussed in rust-lang#31844 (comment), it might be a good idea to warn users of specialization that the feature they are using is unsound. I also expanded the "incomplete feature" warning to link the user to the tracking issue.
… r=matthewjasper Specialization is unsound As discussed in rust-lang#31844 (comment), it might be a good idea to warn users of specialization that the feature they are using is unsound. I also expanded the "incomplete feature" warning to link the user to the tracking issue.
bors
commented
Jun 19, 2020
⌛ Testing commit d1265e7 with merge 25af17199dba15a4206d9f81567b0c6f800d2b04... |
bors
commented
Jun 19, 2020
💔 Test failed - checks-azure |
RalfJung
commented
Jun 19, 2020
@rust-lang/infra there's not even a build log at https://dev.azure.com/rust-lang/rust/_build/results?buildId=32326&view=logs&j=9121965e-722b-5094-4a33-f061e41958d8&t=64b964f2-043e-5afc-0fc3-c41881c5cd34 ? Is there any way to figure out what went wrong here? @bors retry |
emilyalbini
commented
Jun 19, 2020
I guess the underlying VM crashed. Please ping infra again if it starts to happen consistently. |
bors
commented
Jun 19, 2020
⌛ Testing commit d1265e7 with merge 6696efcd9f5e10f076cec28c7322f765345d8c24... |
RalfJung
commented
Jun 19, 2020
Yield. |
…arth Rollup of 16 pull requests Successful merges: - rust-lang#71420 (Specialization is unsound) - rust-lang#71899 (Refactor `try_find` a little) - rust-lang#72689 (add str to common types) - rust-lang#72791 (update coerce docs and unify relevant tests) - rust-lang#72934 (forbid mutable references in all constant contexts except for const-fns) - rust-lang#73027 (Make `need_type_info_err` more conservative) - rust-lang#73347 (Diagnose use of incompatible sanitizers) - rust-lang#73359 (shim.rs: avoid creating `Call` terminators calling `Self`) - rust-lang#73399 (Clean up E0668 explanation) - rust-lang#73436 (Clean up E0670 explanation) - rust-lang#73440 (Add src/librustdoc as an alias for src/tools/rustdoc) - rust-lang#73442 (pretty/mir: const value enums with no variants) - rust-lang#73452 (Unify region variables when projecting associated types) - rust-lang#73458 (Use alloc::Layout in DroplessArena API) - rust-lang#73484 (Update the doc for std::prelude to the correct behavior) - rust-lang#73506 (Bump Rustfmt and RLS) Failed merges: r? @ghost
See rust-lang/rust#71420. This doesn't need a release (or a changelog entry) as it just fixes a warning.
See rust-lang/rust#71420. This doesn't need a release (or a changelog entry) as it just fixes a warning.
As discussed in #31844 (comment), it might be a good idea to warn users of specialization that the feature they are using is unsound.
I also expanded the "incomplete feature" warning to link the user to the tracking issue.