Pattern matching on unsafe pointers doesn't work
Open
Nobody has claimed this yet.
T-lang
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Saturday Jun 08, 2013 at 04:36 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/7010
This issue was labelled with: A-codegen, A-parser, B-clarifying in the Rust repository
I've wanted it at least once.
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 with the earlier discussion in rust-lang/rust#7010; this issue names no files, tests, or entry points. The desired behavior and completion criteria are not specified, so scope and a validation plan need to be established before implementation.
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
- 15/100