-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Documentation build failed for teloxide
v0.10.1
#99663
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Do you have a more concise way of reproducing this? I can't seem to get it to ICE when I run with |
nvm, should be using |
This is actually reproducible even with Command for reproduction: Backtrace
We don't use |
I found an MRE. I'll put up a fix in a second. |
I found a MRE too :( #![feature(type_alias_impl_trait)]
#[pin_project::pin_project]
pub struct Send {
#[pin]
__: tait::Send,
}
mod tait {
pub(crate) type Send = impl ::core::future::Future<Output = ()>;
pub(crate) fn _def() -> Send {
async {}
}
} |
+1, I basically reproduced that in the UI test https://github.com/rust-lang/rust/pull/99666/files#diff-269b1c1ea2d431a283067ef6982b52c20379f0631bc6d3714cc2cfb1429907e0 but manually expanding the part of the |
Restore `Opaque` behavior to coherence check Fixes rust-lang#99663. This broke in 84c3fcd. I'm not exactly certain that adding this behavior back is necessarily correct, but at least the UI test I provided may stimulate some thoughts. I think delaying a bug here is certainly not correct in the case of opaques -- if we want to change coherence behavior for opaques, then we should at least be emitting a new error. r? `@lcnr`
The full log is available from this link: https://docs.rs/crate/teloxide/0.10.1/builds/597656.
Meta
From the aforementioned link:
The text was updated successfully, but these errors were encountered: