Skip to content

[CoroutineAccessors] Add read and modify. #2853

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

Closed
wants to merge 3 commits into from

Conversation

nate-chandler
Copy link
Contributor

Enable parsing the new keywords behind the CoroutineAccessors experimental feature.

@nate-chandler
Copy link
Contributor Author

swiftlang/swift#76526

@swift-ci please test

@@ -628,6 +632,8 @@ public enum Keyword: CaseIterable {
return KeywordSpec("protocol", isLexerClassified: true)
case .public:
return KeywordSpec("public", isLexerClassified: true)
case .read:
return KeywordSpec("read")
Copy link
Member

Choose a reason for hiding this comment

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

Should read also be behind an experimental feature, like modify?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks! Fixed.

""",
experimentalFeatures: .coroutineAccessors
)
}
Copy link
Member

Choose a reason for hiding this comment

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

Could you also add a test case that read and modify are not parsed when the .coroutineAccessors experimental features is not specified?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep--added one for each.

@nate-chandler
Copy link
Contributor Author

Accidentally opened this PR from a branch in this repo rather than my fork. Closing in favor of the one from my fork: #2855 .

@nate-chandler nate-chandler deleted the general-coro/20240917/1 branch September 18, 2024 00:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants