Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Create stability dashboard #13541

Closed
brson opened this issue Apr 16, 2014 · 2 comments · Fixed by #15586
Closed

Create stability dashboard #13541

brson opened this issue Apr 16, 2014 · 2 comments · Fixed by #15586

Comments

@brson
Copy link
Contributor

brson commented Apr 16, 2014

Making progress on library stability visible should provide incentive to keep stabilizing, shows users that we're making progress, even if we don't have a lot of stable libs.

Just have the nightly snapshots generate some HTML listing everything in the libs and there stability levels.
@pnkfelix
Copy link
Member

sub- or super-task of #13540

@pnkfelix
Copy link
Member

(dropping I-nominated, it should inherit whatever #13540 has.)

@aturon aturon mentioned this issue Jul 10, 2014
Merged
aturon added a commit to aturon/rust that referenced this issue Jul 11, 2014
@aturon
rustdoc: Add stability dashboard
4d16de0 
This commit adds a crate-level dashboard summarizing the stability
levels of all items for all submodules of the crate.

The information is also written as a json file, intended for consumption
by pages like http://huonw.github.io/isrustfastyet/

Closes rust-lang#13541
bors added a commit that referenced this issue Jul 11, 2014
@bors
auto merge of #15586 : aturon/rust/stability-dashboard, r=alexcrichton
1e40115 
This PR adds a crate-level dashboard summarizing the stability levels of all items for all submodules of the crate.

The information is also written as a json file, intended for consumption by pages like http://huonw.github.io/isrustfastyet/

Along the way, fixes a few bugs in stability tracking and places where rustdoc was not pulling the existing stability data.

Closes #13541
notriddle pushed a commit to notriddle/rust that referenced this issue Nov 10, 2022
@bors
Auto merge of rust-lang#13541 - Veykril:dbg-cmd, r=Veykril
66900a7 
Clarify what commands are debug commands in VSCode

Renders as
![image](https://user-images.githubusercontent.com/3757771/199828895-4d7691f6-5c33-405c-9842-691b32745919.png)
flip1995 pushed a commit to flip1995/rust that referenced this issue Oct 18, 2024
@bors
Auto merge of rust-lang#13541 - xFrednet:0-module-name-rep, r=blyxyas
43e99e5 
Move `clippy::module_name_repetitions` to `restriction` (from `pedantic`)

Rational:
- Too pedantic IMO, I use `#[warn(pedantic)]` in my personal projects, but then always allow this lint. The fact that we had a few `#[expect(clippy::module_name_repetitions)]` also underlines this point IMO
- STD doesn't do this either. Examples:
  - std::vec::Vec
  - std::collections::vec_deque::VecDequeue
- rust-lang#7666 commonly ignored

---

changelog: Move [`module_name_repetitions`] to `restriction` (from `pedantic`)
[rust-lang#13541](rust-lang/rust-clippy#13541)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

rustdoc: add stability dashboard aturon/rust
2 participants
@brson @pnkfelix