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

Confusing use of "that" #3576

Open
eshmoylova opened this issue Sep 19, 2024 · 1 comment
Open

Confusing use of "that" #3576

eshmoylova opened this issue Sep 19, 2024 · 1 comment
Labels
clarification Specification of feature is unclear, but not incorrect

Comments

@eshmoylova
Copy link
Member

In reviewing #3545, I tried to read what is supposed to happen with modifications on constrainedby clause in Section 7.3.2, and I found that I cannot fully understand this sentence:

The modifiers for subsequent redeclarations and constraining type are the modifiers on the component or short-class-definition if that is used in the original declaration, otherwise empty.

What does "that" in "if that is used" refers to? The way it is written it appears to refer to component or short-class-definition. Or even just the short-class-definition. But if short-class-definition is not used, then we fall into "otherwise empty" which does not make sense. And it's the modifiers that are supposed to be empty, right?

@eshmoylova eshmoylova added the clarification Specification of feature is unclear, but not incorrect label Sep 19, 2024
@HansOlsson
Copy link
Collaborator

I believe we can skip text here and just write:

The modifiers for subsequent redeclarations and constraining type are the modifiers on the original component or short-class-definition.

.
The modifiers are often empty - but we don't have to make a separate rule to ignore them in that case (as they don't matter); especially if it just causes more confusion. We could non-normatively add that they are often empty, but I don't see it as needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Specification of feature is unclear, but not incorrect
Projects
None yet
Development

No branches or pull requests

2 participants