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
|, ^, and & character class set operators #5922
Comments
From @briandfoyThe |, ^, and & character class (and Unicode property) set operators > / <[abc] | [def]> / These are documented in https://docs.perl6.org/language/regexes but are |
From @jnthnOn Tue, 27 Dec 2016 14:32:45 -0800, comdog wrote:
I doubt they'll be implemented particularly soon; I suggest they are removed from the docs. |
The RT System itself - Status changed from 'new' to 'open' |
From @cokeOn Fri, 30 Dec 2016 13:36:03 -0800, jnthn@jnthn.net wrote:
Opened a docs ticket to cover it. Rejecting this ticket. -- |
@coke - Status changed from 'open' to 'rejected' |
From @briandfoyI notice that in many other places in the docs there are "NYI" annotations. Perhaps that would be appropriate here. I figure that this ticket would need to come back to satisfy the UTS #18 (http://www.unicode.org/reports/tr18/tr18-19.html) support. Perhaps mark it as stalled? |
1 similar comment
From @briandfoyI notice that in many other places in the docs there are "NYI" annotations. Perhaps that would be appropriate here. I figure that this ticket would need to come back to satisfy the UTS #18 (http://www.unicode.org/reports/tr18/tr18-19.html) support. Perhaps mark it as stalled? |
@briandfoy - Status changed from 'rejected' to 'stalled' |
From @briandfoyIf these are intended to be future features (and for Unicode |
The RT System itself - Status changed from 'stalled' to 'open' |
From @AlexDanielI've raised this question too ( https://irclog.perlgeek.de/perl6/2016-12-31#i_13827103 ), but according to Coke: Perhaps someone can doublecheck, but looks like there's no reason to keep this open. On 2017-01-02 13:27:48, comdog wrote:
|
From @briandfoyIf it's going to be rejected, a note about why Perl 6 will not have |
From @AlexDanielOn 2017-01-02 13:51:27, comdog wrote:
I'm not sure I understand the issue here… So if you want something like <:Ll + :N>, then it already works. Now, the only question is how would you do intersections, in which case you can use something like this: say ‘pyõrl6’ ~~ m/[<:Ll> & <:Block(‘Basic Latin’)>]+/ # OUTPUT«「py」» I don't mind & being added, as much as I don't mind it being rejected. But I don't really see the point about basic unicode support (or the lack of thereof). Perhaps you can clarify? |
From @jnthnOn Mon, 02 Jan 2017 14:15:45 -0800, alex.jakimenko@gmail.com wrote:
To be clear, my "doubt they'll be implemented soon" wasn't an indication they shouldn't be, just that it's better that the docs cover things that actually exist. If somebody popped up with a patch to implement them tomorrow, that'd be just great. But, as mentioned by Alex, there is already a way to do it, and at the moment most folks are more focused on making the many features we already have robust and fast rather than adding more features. Thus my uncertainty whether it'll top anybody's todo list especially soon. Of course, now I've written this somebody will probably be like "hah, challenge accepted!" :-) I'll re-title this ticket to be an NYI for the features; it's right that we have a ticket to track that it wants doing at some point. /jnthn |
From @AlexDanielAlso: “I notice that in many other places in the docs there are "NYI" annotations.” Please file doc tickets for these. Most of the time we don't want to doc NYI stuff. On 2016-12-30 23:24:46, comdog wrote:
|
Migrated from rt.perl.org#130419 (status was 'open')
Searchable as RT130419$
The text was updated successfully, but these errors were encountered: