From: kasumi@rollingapple.net
To: ruby-core@ruby-lang.org
Subject: [ruby-core:99553] [Ruby master Bug#17113] /\K/ in separator for String#split behaves differently than /(?<=)/
Date: Tue, 11 Aug 2020 09:59:35 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-17113.20200811095934.13465@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17113.20200811095934.13465@ruby-lang.org
Issue #17113 has been reported by hanazuki (Kasumi Hanazuki).
----------------------------------------
Bug #17113: /\K/ in separator for String#split behaves differently than /(?<=)/
https://bugs.ruby-lang.org/issues/17113
* Author: hanazuki (Kasumi Hanazuki)
* Status: Open
* Priority: Normal
* ruby -v: ruby 2.8.0dev (2020-08-11T07:51:07Z master 5af983af4f) [x86_64-linux]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
When a String is `#split`ted with a pattern containing /\K/ (lookbehind) operator,
the portion that matches the lookbehind pattern will not appear in the result.
```ruby
"abcd".split(/b\Kc/) # => ["a", "d"]
"abcd".split(/(?<=b)c/) # => ["ab", "d"] -- expected result
```
In this example, since `/b\Kc/` matches `"c"` in `"abcd"`, the result is expected to be `["ab", "d"]`. Actually `["a", "d"]` is returned.
`(?<=)` operator seems to work expectedly.
--
https://bugs.ruby-lang.org/
next parent reply other threads:[~2020-08-11 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 9:59 kasumi [this message]
2020-08-11 10:03 ` [ruby-core:99554] [Ruby master Bug#17113] /\K/ in separator for String#split behaves differently than /(?<=)/ kasumi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-17113.20200811095934.13465@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).