rust-lang / rust-lang/rust-analyzer
Revive the librarification effort
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Our fork of rustc_abi is quite outdated by now, and unfortunately upstream broke the non nightly build of it (and worse, removed all the generic parameters we depended on) so we can't update it anymore without putting in significant effort into fixing that. This will most likely be a recurring thing so maybe it is time to revive the librarification effort (and potentially crate a working group for that) to lay out a proper plan for such crates. Or at least properly librarify the rustc_abi crate (that is no ugly nightly cfgs)
Obviously not the best place to have this discussion right now, but putting it down here as a reminder (to myself at least).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the forked rustc_abi and the upstream Rust PR #107163, focusing on the removed generic parameters and the broken non-nightly build. Done would require an agreed librarification plan, or a properly librarified rustc_abi without the current nightly-only cfgs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100