rust-lang / rust-lang/reference
Constant Evaluation: clarifications needed
Open
Nobody has claimed this yet.
A-const-eval
Language Cleanup
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 607
- PR merge metrics
- PR metrics pending
Description
I'm quoting this page:
Constant evaluation is the process of computing the result of expressions during compilation.
Q) How does it look like? Please demonstrate
Only a subset of all expressions can be evaluated at compile-time.
Q) Which expressions in particular?
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 with the Rust Reference's const_eval.html page and inspect the two quoted statements about constant evaluation. Add a clear demonstration of how constant evaluation looks and identify which expressions can be evaluated at compile time, with examples that answer both questions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100