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
The Unstable Book in section foo leads to a tracking issue #1234, which is about an unrelated topic rust-mac1 bot has issues. The naming of both the feature and the issue leads me to believe they are only given as examples in the code and are being incorrectly picked up by the documentation generator as real ones.
For instance they are used in library/core/src/intrinsics.rs:
//! In order to make an intrinsic usable at compile-time, one needs to copy the implementation//! from https://github.com/rust-lang/miri/blob/master/src/shims/intrinsics.rs to//! `librustc_mir/interpret/intrinsics.rs` and add a//! `#[rustc_const_unstable(feature = "foo", issue = "01234")]` to the intrinsic.
The text was updated successfully, but these errors were encountered:
camelid
added
C-bug
Category: This is a bug.
A-docs
Area: documentation for any part of the project, including the compiler, standard library, and tools
labels
Oct 20, 2020
…mulacrum
Ignore commented out lines when finding features
This fixesrust-lang#76246, where commented out lines were being detected as features by `tidy`, by ignoring those lines when looking for features. It's still not perfect, since it can be fooled by things like:
```rust
/*
#[unstable(feature = "foo", issue = "1234")]
*/
```
But luckily that never happens in `rustc`, so `foo` now ceases to appear in the unstable book.
jackh726
added a commit
to jackh726/rust
that referenced
this issue
Apr 28, 2021
…mulacrum
Ignore commented out lines when finding features
This fixesrust-lang#76246, where commented out lines were being detected as features by `tidy`, by ignoring those lines when looking for features. It's still not perfect, since it can be fooled by things like:
```rust
/*
#[unstable(feature = "foo", issue = "1234")]
*/
```
But luckily that never happens in `rustc`, so `foo` now ceases to appear in the unstable book.
jackh726
added a commit
to jackh726/rust
that referenced
this issue
Apr 29, 2021
…mulacrum
Ignore commented out lines when finding features
This fixesrust-lang#76246, where commented out lines were being detected as features by `tidy`, by ignoring those lines when looking for features. It's still not perfect, since it can be fooled by things like:
```rust
/*
#[unstable(feature = "foo", issue = "1234")]
*/
```
But luckily that never happens in `rustc`, so `foo` now ceases to appear in the unstable book.
The Unstable Book in section foo leads to a tracking issue #1234, which is about an unrelated topic
rust-mac1 bot has issues
. The naming of both the feature and the issue leads me to believe they are only given as examples in the code and are being incorrectly picked up by the documentation generator as real ones.For instance they are used in
library/core/src/intrinsics.rs
:The text was updated successfully, but these errors were encountered: