Figure out how to check that `minicore` matches signatures of real `core`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Currently, there's no safeguard to guard against minicore signatures and type definitions drifting/diverging from that of the real core, which is very much not ideal. We should figure out a way to check if the signatures (and type definitions, where applicable) match between minicore and real core.
One related issue that may help with this is to use host core when available but that in itself is insufficient (and can cause complications where something only fails on targets where host core isn't available).
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 reading this issue and the related issue #134652 about using host core when available. Investigate where minicore and real core signatures and applicable type definitions are maintained, then define a check that reliably detects divergence across targets. Done means an automated safeguard compares them and covers cases where host core is unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100