-
Notifications
You must be signed in to change notification settings - Fork 41
Add dev guide #686
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
tshepang
merged 1 commit into
rust-lang:main
from
kirtchev-adacore:fls-685-create-fls-dev-guide
Apr 7, 2026
Merged
Add dev guide #686
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,87 @@ | ||
| .. SPDX-License-Identifier: MIT OR Apache-2.0 | ||
| SPDX-FileCopyrightText: The Rust Project Contributors | ||
|
|
||
| .. default-domain:: spec | ||
|
|
||
| .. informational-page:: | ||
|
|
||
| Developer Guide | ||
| =============== | ||
|
|
||
| This document outlines the various formats, processes, and procedures associated with the maintenance of the FLS. | ||
|
|
||
| Changelog maintenance | ||
| --------------------- | ||
|
|
||
| The Changelog is located in ``src/changelog.rst``. It should be updated using one of the sentence patterns outlined below. Note that this is not an exhaustive list, and special cases would need to use their own wording. | ||
|
|
||
| No change | ||
| ~~~~~~~~~ | ||
|
|
||
| When an entry in the Rust Release Notes does not affect the FLS, provide the reason as to why this is the case. Below are a few examples of such justifications:: | ||
|
|
||
| - Lints are outside the scope of the FLS | ||
| - Target XYZ is outside the scope of the FLS | ||
| - The exact mechanics of the borrow checker are outside the scope of the FLS | ||
| - The restriction was not specified in the FLS | ||
| - Configuration options are environment-specific and not exhaustive | ||
|
|
||
| Glossary entries | ||
| ~~~~~~~~~~~~~~~~ | ||
|
|
||
| When working with glossary entries, use the following sentence pattern for a single glossary entry:: | ||
|
|
||
| <Action> glossary entry: :t:`term` | ||
|
|
||
| Use the following sentence pattern for multiple paragraphs:: | ||
|
|
||
| <Action> glossary entries: | ||
| - :t:`term` | ||
| - :t:`term` | ||
|
|
||
| ``<Action>`` must denote either ``Changed``, ``New``, or ``Removed``. | ||
|
|
||
| Paragraphs | ||
| ~~~~~~~~~~ | ||
|
|
||
| When working with paragraphs, use the following sentence pattern for a single paragraph:: | ||
|
|
||
| <Action> paragraph: :p:`fls_paragraph_id` | ||
|
|
||
| Use the following sentence pattern for multiple paragraphs:: | ||
|
|
||
| <Action> paragraphs: | ||
| - :p:`fls_paragraph_id` | ||
| - :p:`fls_paragraph_id` | ||
|
|
||
| ``<Action>`` must denote either ``Changed``, ``Moved``, ``New``, or ``Removed``. | ||
|
|
||
| Sections | ||
| ~~~~~~~~ | ||
|
|
||
| When working with sections, use the following sentence pattern for a single section:: | ||
|
|
||
| <Action> section :ref:`fls_section_id` | ||
|
|
||
| Use the following sentence pattern for multiple sections:: | ||
|
|
||
| <Action> sections: | ||
| - :ref:`fls_section_id` | ||
| - :ref:`fls_section_id` | ||
|
|
||
| ``<Action>`` must denote either ``Moved``, ``New``, or ``Removed``. | ||
|
|
||
| Syntax | ||
| ~~~~~~ | ||
|
|
||
| When working with syntax, use the following sentence pattern for a single syntax category:: | ||
|
|
||
| <Action> syntax: :s:`syntax_category` | ||
|
|
||
| Use the following sentence pattern for multiple syntax categories:: | ||
|
|
||
| <Action> syntax: | ||
| - :s:`syntax_category` | ||
| - :s:`syntax_category` | ||
|
|
||
| ``<Action>`` must denote either ``Changed``, ``New``, or ``Removed``. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -41,6 +41,7 @@ FLS | |
| licenses | ||
| glossary | ||
| undefined-behavior | ||
| dev-guide | ||
| changelog | ||
| background | ||
|
|
||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure we want to document glossary entries since they are informational content (and we are planning to have them be mere duplicates of main content anyways)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should keep this part in for now. Once the glossary generation machinery is in, we will remove this part.