The new unsafety definition
Nobody has claimed this yet.
- Dominant language
- reStructuredText
- Stars
- 497
- Forks
- 41
- Avg merge
- 3h 52m
- Merged PRs (30d)
- 4
Description
The new unsafety definition (after https://github.com/ferrocene/specification/pull/395) is:
An unsafe operation is an operation that may result in undefined behavior that is not diagnosed as a static error.
Someone may argue that safe operations can also "result" in UB (due to some unsoundness in an abstraction or a broken contract), thus many more operations are unsafe than the ones stated in the list. Perhaps some clarification on "result" would help, or a different way to express the idea.
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 proposed unsafety definition in this issue and review the referenced specification pull request #395 for context. Determine whether “result in undefined behavior” needs clarification or whether the definition should be expressed differently; done means reaching an agreed, unambiguous wording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100