Skip to content

Conversation

natecook1000
Copy link
Member

PatternConverter uses one last AST-based API defined in _StringProcessing, which is technically not allowed but not
problematic b/c PatternConverter also imports _RegexParser. However, this can have compile-time problems later on, so this changes the entry point for PatternConverter to just use an Any parameter that is checked at runtime to actually be AST.

Cherry pick of #416, resolves rdar://92876793.

PatternConverter uses one last AST-based API defined in
_StringProcessing, which is technically not allowed but not
problematic b/c PatternConverter also imports _RegexParser.
However, this can have compile-time problems later on, so
this changes the entry point for PatternConverter to just use
an Any parameter that is checked at runtime to actually be AST.
@natecook1000
Copy link
Member Author

@swift-ci Please test

@natecook1000 natecook1000 added the r5.7 5.7 Release Cherry Picks label May 16, 2022
@natecook1000 natecook1000 merged commit d3bd66c into swiftlang:swift/release/5.7 May 16, 2022
natecook1000 added a commit to natecook1000/swift-experimental-string-processing that referenced this pull request May 16, 2022
…tlang#417)

PatternConverter uses one last AST-based API defined in
_StringProcessing, which is technically not allowed but not
problematic b/c PatternConverter also imports _RegexParser.
However, this can have compile-time problems later on, so
this changes the entry point for PatternConverter to just use
an Any parameter that is checked at runtime to actually be AST.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

r5.7 5.7 Release Cherry Picks

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants