Should we output an error for loose expressions, or functions' return values being discarded?
Open
Nobody has claimed this yet.
Language Design
- Dominant language
- Rust
- Stars
- 126
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Right now having the error is an issue, since it breaks assert #()
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 reproducing the assert #() case and tracing where the compiler reports errors for loose expressions or discarded function return values. The issue does not name files or tests; done requires an explicit decision on the intended diagnostic behavior and confirming that assert #() works accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100