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.

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

s/|w/?wb/ (switch from Rakudo feature to Raku feature) #866

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

raiph
Copy link

@raiph raiph commented Nov 19, 2024

It's OK if this PR is left to sit, or is rejected, but I'm posting it to tie up the last loose end) I'm aware of regarding <|w>.

A search of roast for |w reveals one match, just one, no more, no less.

That demonstrates that although |w was "spec"d (speculated) in the design docs as one of a range of <|X> features (where X is a character class), and is implemented in Rakudo, it is not (currently) roasted, and as the discussion about this in the doc repo, led to its removal from the Raku doc, I decided to write this PR.

It's OK if this PR is left to sit, or is rejected, but I'm posting it to tie up the last [loose end](Raku/doc#4435.)) I'm aware of regarding `<|w>`.

[A search of roast for `|w` reveals one match, just one, no more, no less](https://github.com/search?q=repo%3ARaku%2Froast+%22%3C%7Cw%22&type=code).

That demonstrates that although `|w` was "spec"d (speculated) in the design docs as one of a range of `<|X>` features (where `X` is a character class), and is implemented in Rakudo, it is not (currently) roasted, and as the [discussion about this in the doc repo](Raku/doc#4435), led to its removal from the Raku doc, I decided to write this PR.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant