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.

Sign up for GitHub

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

Jump to bottom

Regex DSL Status #131

Open
9 of 13 tasks
milseman opened this issue Jan 26, 2022 · 2 comments
Open
9 of 13 tasks

Regex DSL Status #131

milseman opened this issue Jan 26, 2022 · 2 comments

Comments

@milseman
Copy link
Collaborator

milseman commented Jan 26, 2022 •
edited by rxwei
Loading

This tracks the status and progress of built-in result builder DSL APIs. It doesn't necessarily reflect other related API, the protocols used for library extension, or API details beyond result builders such as options and custom character classes.

See #63 and #132

Current Status

  • Concatenation
  • Alternation
  • Quantification
    • Shorthand operators (.?, .*, .+)
  • Conditional
  • Backreferences
  • Anchors
  • Lookaround assertions
  • Built-in character classes
  • Named subpatterns and subpattern invocations
  • Pattern inversions
  • Options and option scopes
  • Redundantly named captures, branch-reset, etc

Needed

  • Conditional patterns
  • Pattern inversions
  • Options and option scopes
  • Redundantly named captures, branch-reset, etc
  • Built-in properties
  • Balancing groups
  • Recursion level for backreferences
  • Named captures
  • TBD

Type system concerns / impact

TBD

Structural and flat captures

TBD
@stephentyrone
Copy link
Member

#155

@milseman
Copy link
Collaborator Author

milseman commented May 6, 2022

@rxwei can you incorporate anything here into separate issues (if this release) or #370 for future? After that, we can close this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@milseman @stephentyrone