-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rustc panic when running cargo doc
in AutoTraitFinder::find_auto_trait_generics
#72213
Comments
somewhat minified: struct Lines<'a, L>
where
L: Iterator<Item = &'a ()>,
{
words: std::iter::Peekable<Words<'a, L>>,
}
struct Words<'a, L> {
_m: std::marker::PhantomData<&'a L>,
}
impl<'a, L> Iterator for Words<'a, L>
where
L: Iterator<Item = &'a ()>,
{
type Item = ();
fn next(&mut self) -> Option<Self::Item> {
unimplemented!()
}
} |
Somewhat interesting: nightly-2018-01-17 gives me:
and cargo check as gives me the same error message. On nightly-2019-01-17 on the other hand cargo doc panics and cargo check does not complain any more:
Edit: nightly-2018-12-01 gives me exactly no output. No warning, no ICE. That is weird as well... |
Regression in nightly-2018-12-08 (14997d5...4a45578) (nightly-2018-12-07 is not available) The "no output" regression (from rejecting the program as such and giving no output at all) is in nightly-2018-09-13 (2f1547c...f2302da) |
The latter is an intended change caused by #53793 |
This is still occurring, the panic seems to come from this line in Updated info:
Error output
Backtrace
|
cargo doc
: Unable to fulfill trait DefId(2:1922cargo doc
in AutoTraitFinder::find_auto_trait_generics
Assigning |
…nikomatsakis Handle projection predicates in the param env for auto-trait docs Fixes rust-lang#72213 Any predicates in the param env are guaranteed to hold, so we don't need to do any additional processing of them if we come across them as sub-obligations of a different predicate. This allows us to avoid adding the same predicate to the computed ParamEnv multiple times (but with different regions each time), which causes an ambiguity error during fulfillment.
rustc panic when running
cargo doc
. The crate otherwise seems to test, run & work fine.Steps to reproduce
ca74e6a25b26eed68b9513363bb45167a3729cd3
.cargo doc -p glyph_brush_layout
.Meta
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: