I think there's a slight mismatch between the Chapter divisions that we have, which is based on the FLS' division of the Rust Language:
Note: the first 3 chapters of the FLS were omitted: "General", "Lexical Elements", and "Items"
The FLS division makes a lot of sense, at least as a baseline, for talking about elements of the language in a normative fashion. But it has two important caveats: Where does the interaction with system APIs fall?, and more generally perhaps: Where does the usage of core, std and other foundational libraries fall?
This mismatch means that the guidelines that stem from #392 (baseline recommendations for filesystem API usage) currently have nowhere to go. It also means that currently #370 is getting added to the Program Structure and Compilation chapter.
I believe this is a mismatch that will continue asking us to place guidelines in chapters where they don't really make sense, just to be able to include them in the document.
How should we solve this?
I'm thinking that perhaps we could have another chapter. I'm not sure. Using the FLS as a skeleton makes sense from a normative standpoint, but it might have other problems apart from this one. Maybe we could use something else. I don't know yet.
I think there's a slight mismatch between the Chapter divisions that we have, which is based on the FLS' division of the Rust Language:
Coding Guidelines' Chapters
FLS Chapters
The FLS division makes a lot of sense, at least as a baseline, for talking about elements of the language in a normative fashion. But it has two important caveats: Where does the interaction with system APIs fall?, and more generally perhaps: Where does the usage of
core,stdand other foundational libraries fall?This mismatch means that the guidelines that stem from #392 (baseline recommendations for filesystem API usage) currently have nowhere to go. It also means that currently #370 is getting added to the Program Structure and Compilation chapter.
I believe this is a mismatch that will continue asking us to place guidelines in chapters where they don't really make sense, just to be able to include them in the document.
How should we solve this?
I'm thinking that perhaps we could have another chapter. I'm not sure. Using the FLS as a skeleton makes sense from a normative standpoint, but it might have other problems apart from this one. Maybe we could use something else. I don't know yet.