runtimeverification/stable-mir-json

Qualified names for both `IntrinsicSym` and `NormalSym`

Open

#137 opened on Mar 5, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (5 forks)auto 404
good first issue

Repository metrics

Stars
 (10 stars)
PR merge metrics
 (PR metrics pending)

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

This comment for some more context

Contributor guide

Research direction
Implement qualified name extraction for IntrinsicSym and NormalSym by demangling symbols and mapping to paths using compiler metadata.
Tech stack
rust
Domain
tooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50