runtimeverification / runtimeverification/stable-mir-json
Qualified names for both `IntrinsicSym` and `NormalSym`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Currently IntrinsicSym serialises with the short name (e.g. black_box) and NormalSym serialises with the mangled name (e.g. _ZN4core9panicking19assert_failed_inner17h1d286061ca0adfe7E). Both have upsides and downsides:
- short name is concise but ambiguous (which
black_box? Hard to tell just by reading) - mangled name is unambiguous but too verbose
#85 was going to use the mangled name for intrinsics, but this would not fix the verbosity problem.
A middle ground for both would be a qualified name
_ZN4core9panicking19assert_failed_inner17h1d286061ca0adfe7E->core::panicking::assert_failed_innerblack_box-> core::intrinsics::black_box or core::hint::black_box
This comment for some more context
Contributor guide
No contributing guide indexed for this repository
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 serialization code for IntrinsicSym and NormalSym, then compare how each currently obtains its symbol name. Use the referenced core/src/intrinsics/mod.rs and core/src/hint.rs definitions to check the intended qualified names for intrinsics. Done means both symbol kinds serialize to concise, unambiguous qualified names, with tests covering the examples and ambiguous intrinsic names.
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
- Mostly clear
- Newbie friendliness
- 35/100