Hello, Swift community.
The second review of SE-0350: Regex Type and Overview begins now and runs through April 28, 2022.
The second revision makes some adjustments to naming:
- Matching functions now follow the pattern
Regex.init(_: String)has dropped its
The proposal also now clarifies that matching will check for task cancellation and throw.
An alternative considered section now discusses the benefits of the bytecode interpreter.
This review is part of a collection of proposals for better string processing in Swift. The proposal authors have put together a proposal overview with links to in-progress pitches and reviews. This proposal introduces the fundamental type,
Regex , to the standard library, and outlines how it will be used, including setting up future proposals. It will be run simultaneously with one of the ways to create the
Regex type: from a result builder DSL .
As with the concurrency initiative last year, the core team acknowledges that reviewing a large number of interlinked proposals can be challenging. In particular, acceptance of one of the proposals should be considered provisional on future discussions of follow-on proposals that are closely related but have not yet completed the evolution review process. Similarly, reviewers should hold back on in-depth discussion of a subject of an upcoming review. Please do your best to review each proposal on its own merits, while still understanding its relationship to the larger feature.
Reviews are an important part of the Swift evolution process. All review feedback should be either on this forum thread or, if you would like to keep your feedback private, directly to the review manager. If you do email me directly, please put "SE-0350" somewhere in the subject line.
The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the direction of Swift. When writing your review, here are some questions you might want to answer in your review:
- What is your evaluation of the proposal?
- Is the problem being addressed significant enough to warrant a change to Swift?
- Does this proposal fit well with the feel and direction of Swift?
- If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
- How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
More information about the Swift evolution process is available at:
As always, thank you for contributing to Swift.