Skip to content
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

Redirect link to normative text #1030

Merged
merged 2 commits into from
Jan 10, 2024

Conversation

RexJaeschke
Copy link
Contributor

[This a trivial, nit-picking edit!]

In draft-v8 §9.4.1 Definite assignment|General we have:

...

Note: Informally stated, the rules of definite assignment are:

...

The formal specification underlying the above informal rules is described in §9.4.2, §9.4.3, and §9.4.4.

end note

The definite-assignment states of instance variables of a struct_type variable are tracked individually as well as collectively. In additional to the rules above, the following rules apply to struct_type variables and their instance variables:

  • ...
  • ...

In V1, the Note content was normative, so the list of rules it contains was normative. However, in V2, the Note bracketing was introduced, making the contents informative. However, the phrase marked in bold/italic was not adjusted accordioning. As a result, that phrase in normative text relies on so-called rules in informative text (which, in turn, point to a normative set of rules).

My solution is simple: Have the the phrase marked in bold/italic point directly to the normative set of rules.

@RexJaeschke RexJaeschke added the meeting: proposal There is an informal proposal in the issue, worth discussing in a meeting label Jan 2, 2024
@RexJaeschke RexJaeschke requested a review from jskeet January 2, 2024 22:47
@RexJaeschke RexJaeschke self-assigned this Jan 2, 2024
@RexJaeschke
Copy link
Contributor Author

The 2nd edit is simply a md rendering issue: The para following the 1-line Note is currently being presented as if it too were a Note, which of course, it isn't.

@jskeet jskeet added the meeting: discuss This issue should be discussed at the next TC49-TG2 meeting label Jan 10, 2024
Copy link
Member

@BillWagner BillWagner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jskeet jskeet merged commit e202391 into dotnet:draft-v8 Jan 10, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meeting: discuss This issue should be discussed at the next TC49-TG2 meeting meeting: proposal There is an informal proposal in the issue, worth discussing in a meeting
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants