oxidecomputer / oxidecomputer/hubris
We're setting `RUSTC_BOOTSTRAP=1` and that's annoying
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
We are now on a "stable" toolchain, which closed out https://github.com/oxidecomputer/hubris/issues/1927
However, we have to set RUSTC_BOOTSTRAP=1 to enable the one feature that we care about, -Zemit-stack-sizes.
We explicitly deny all nightly features with -Zallow-features= (this is the empty list), so no one can use nightly features in Rust code. Unfortunately, once you opt into Nightly Mode™, codegen changes significantly – even with all nightly features banned. This is sad, because it somewhat defeats the purpose of being on stable.
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 locating the repository's Rust toolchain and build configuration that sets RUSTC_BOOTSTRAP=1, enables -Zemit-stack-sizes, and denies nightly features. Investigate whether the required stack-size output can work without Nightly Mode, then verify that the configuration no longer needs the bootstrap override while preserving the existing feature restriction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100