microsoft / microsoft/demikernel
[build] Drop Use of Unstable Features
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 151
- PR merge metrics
- No merged PRs in 30d
Description
Description
We currently rely on the following unstable features:
-
test: mainly used for feature microbenchmarks -
allocator_api: used for implementingWakerPageRef -
new_uninit -
atomic_from_mut -
never_type -
type_alias_impl_trait -
slice_ptr_get -
strict_provenance
Expected Behavior
We should not rely on unstable features at all.
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
No files, tests, or entry points are named. Start by locating uses of each listed unstable Rust feature, then determine what replacements or redesigns are needed; the work is done when the project no longer relies on any unstable features.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100