software-mansion / software-mansion/cairo-debugger
Check compiler config per target in LS debug code lens verification
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7
- Forks
- 2
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 1
Description
Currently, we assume that all targets for the same package have the same compiler config. This can change - see https://github.com/software-mansion/scarb/issues/2981 (one of the solutions is to have per target compiler config, see this slack thread). We should instead do what snforge now does - check here for reasoning.
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 LS debug code lens verification logic and trace where compiler configuration is read for targets in the same package. Compare the current assumption with the per-target validation approach referenced from snforge. Done means verification checks each target's compiler configuration independently, including packages whose targets differ.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100