Handle ambiguous glob import of `panic!`
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 231
- Avg merge
- 19h 55m
- Merged PRs (30d)
- 67
Description
Handle https://github.com/rust-lang/rust/issues/147319. Low priority, but niche enough that we should have it recorded as a potential issue down the line.
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 the linked Rust issue, https://github.com/rust-lang/rust/issues/147319, to understand the expected handling of an ambiguous glob import of panic!. The issue names no gccrs files or tests; done means the specified ambiguity is handled and covered by appropriate regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100