swiftlang / swiftlang/swift-experimental-string-processing

`Anchor.inverted` does not have any effect on most members

Open
#584 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
308
Forks
52
Avg merge
12h 45m
Merged PRs (30d)
2

Description

For:

  • Anchor.startOfSubject
  • Anchor.endOfSubjectBeforeNewline
  • Anchor.endOfSubject
  • Anchor.firstMatchingPositionInSubject
  • Anchor.startOfLine
  • Anchor.endOfLine

Using the inverted member currently has no effect. We ought to implement the right behavior.

rdar://97075024

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the implementations of Anchor.startOfSubject, endOfSubjectBeforeNewline, endOfSubject, firstMatchingPositionInSubject, startOfLine, and endOfLine. Read how Anchor.inverted is handled elsewhere, then determine the expected inverted behavior for each listed member and add coverage demonstrating that it takes effect.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.