Make it clear that the reference isn't normative #35102
Conversation
Any time someone edits the reference, it has to be taken very seriously, since it's the closest thing we have to a specification. This commit adds language which indicates that this is not a normative document, which makes it easier to make tweaks without worrying about forever harming the future of Rust by painting ourselves in a corner.
|
IMO this doesn't solve the problem. What is normative then? Put another way, I don't see why it's bad to think twice before changing the reference. |
|
A PR to the reference is not the place to discuss the finer points of language design and long-term strategy. There are a dozen other venues for it, and the decisions made there already aren't reflected in the reference. So, this document is already not normative in any serious sense. It's bad that there isn't a normative document, but awkwardly stumbling around whenever touching the reference doesn't solve that problem. Edit: This is not to say one shouldn't be careful with what goes in the reference, but not to "OMG if we merge this it's written in stone" levels. |
|
When we produce a normative document, what will it be called? |
|
|
|
/cc @rust-lang/lang @rust-lang/compiler |
|
+1, this describes how I think of the reference |
|
ping @aturon, (reviewer) |
|
@bors: r+ rollup |
|
📌 Commit daf2d7d has been approved by |
|
⌛ Testing commit daf2d7d with merge 9a496b4... |
|
💔 Test failed - auto-linux-cross-opt |
|
@bors: retry On Mon, Nov 7, 2016 at 5:21 PM, bors [email protected] wrote:
|
Make it clear that the reference isn't normative Any time someone edits the reference, it has to be taken very seriously, since it's the closest thing we have to a specification. This commit adds language which indicates that this is not a normative document, which makes it easier to make tweaks without worrying about forever harming the future of Rust by painting ourselves in a corner. r? @aturon
Any time someone edits the reference, it has to be taken very seriously,
since it's the closest thing we have to a specification. This commit
adds language which indicates that this is not a normative document,
which makes it easier to make tweaks without worrying about forever
harming the future of Rust by painting ourselves in a corner.
r? @aturon