Policy: What can be left undefined?

rust-lang / spec

The Rust specification

Apache License 2.0

103 stars 7 forks source link

Policy: What can be left undefined? #28

Open ehuss opened 8 months ago

ehuss commented 8 months ago

Should we ever allow anything to be left undefined? If so, should the particular undefined parts be explicitly stated, and how?

ehuss's preference is to never leave anything undefined, but there will definitely be some gray areas that make that difficult.

chorman0773 commented 7 months ago

My $0.02: Once a chapter is written, that chapter should be as complete as possible. Things that aren't given a specific choice should be marked as implementation-defined, unspecified, target-specific, or undefined as appropriate. If the choice isn't known, determining what that choice is should be part of writing the chapter.

digama0 commented 7 months ago

...or "spec hole", along with a tracking issue and/or some indication of what team would need to be responsible for making a decision needed to close the hole.