You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Culprit found: the derives on top of the deprecated type.
#[deprecated(note="Use std .step_by() instead", since="0.8")]#[derive(Clone,Debug)]#[must_use = "iterator adaptors are lazy and do nothing unless consumed"]pubstructStep<I>{iter:Fuse<I>,skip:usize,}
Inserting an#[allow(deprecated)] on the deprecated struct silences the mystery warning.
bluss
changed the title
Deprecation warning emitted by rustc without a span
Deprecation warning emitted from derive without a span
Nov 24, 2018
deriving: avoid dummy Span on an artificial `type_ident` path
The dummy Span pointed to the beginning of the source file instead to where the `#[derive]` is located. Later, it tripped the `in_derive_expansion(span)` check at `src/librustc/middle/stability.rs`, causing a span-less deprecation warning to be emitted.
Fixesrust-lang#56195, Fixesrust-lang#55417.
Reproducing code:
Emits (without line numbers)
(Old report)
In this branch / commit of itertools, running
cargo build
shows a deprecation error without location in the code.Version: rustc 1.32.0-nightly (1f57e48 2018-11-23)
The text was updated successfully, but these errors were encountered: