Merge main into release/6.2 #3111
Closed
Conversation
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
Make `@abi` non-experimental
This unfortunately ends up causing CI checks to reset and always skipped after marking a PR ready for review.
Update the allowed user for publishing releases to bnbarham
[CI] Remove skip for ready for review
Add more code owners
Add trailing comma support in cases missing from Swift 6.1
Add support to parse the non-underscored version of the @specialized attribute. rdar://150033316
`Macro.Type` is used in various `Error`s and since SE-0470, needs to conform to `SendableMetatype`.
Add a `SendableMetatype` conformance to `Macro`
Add support for SE-0460 @specialized
Change InlineArray sugar separator `x` -> `of`
…ental feature This is an alternative spelling of `typealias DefaultIsolation = (MainActor | nonisolated)` that was proposed as part of SE-0478. `using` declaration accepts an attribute or a modifier and currently could be used to set a default actor isolation per file, but could be extended to support other use-cases in the future. Implementation uses `DefaultIsolationPerFile` experimental feature flag to hide the syntax.
[SwiftParser] SE-0478: Implement `using` declaration under an experim…
Update `ExpandEditorPlaceholdersToLiteralClosures` and `CallToTrailingClosures` such that they can handle macro expansion exprs and decls. This unfortunately requires changing them such that they take a `Syntax` input and output to satisfy the conformance to `SyntaxRefactoringProvider`, but that seems preferable to making the refactoring types themselves generic. If in the future we decide to expose `CallLikeSyntax` as a public protocol, we could decide to expose additional generic `refactor` overloads here. However it's not clear there's enough clients of these APIs to motivate doing that in this PR.
Handle macro expansion args in placeholder expansion
The only place where we were dropping unexpected tokens or trivia around a string segment was when inferring the indentation of the closing quote. Instead of having a precondition, add the conditions that the last segment doesn’t have any of these here and fall back to the same logic that is used when the indentaiton could not be inferred. Fixes #3097
Relax precondition in `postProcessMultilineStringLiteral`
…el in a closure not followed by a colon There was a mismatch between the call to `eat` and `at`. Switch the pair to a `consume(if:)` to avoid the issue. Fixes #3103
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
This PR was automatically opened by a GitHub action. Review the changes included in this PR and determine if they should be included in the release branch. If yes, merge the PR. Otherwise revert changes that should not be included on this branch.