From: "sisyphus_cg (Sisyphus CG) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "sisyphus_cg (Sisyphus CG)" <noreply@ruby-lang.org>
Subject: [ruby-core:115924] [Ruby master Bug#20095] Regex lookahead behaving strangely in 3.3.0
Date: Wed, 27 Dec 2023 05:08:28 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-20095.20231227050827.53096@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-20095.20231227050827.53096@ruby-lang.org
Issue #20095 has been reported by sisyphus_cg (Sisyphus CG).
----------------------------------------
Bug #20095: Regex lookahead behaving strangely in 3.3.0
https://bugs.ruby-lang.org/issues/20095
* Author: sisyphus_cg (Sisyphus CG)
* Status: Open
* Priority: Normal
* ruby -v: 3.3.0
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
Multiple regex lookaheads seem to behave strangely in 3.3.0:
```ruby
p "xxx" =~ /(?=.*x)x(?=banana)/ # 2
```
Clearly, the string `xxx` does not contain `banana`, so this regex should never match, but it does.
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/
next parent reply other threads:[~2023-12-27 5:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 5:08 sisyphus_cg (Sisyphus CG) via ruby-core [this message]
2023-12-28 14:55 ` [ruby-core:115961] [Ruby master Bug#20095] Regex lookahead behaving strangely in 3.3.0 dentarg (Patrik Ragnarsson) via ruby-core
2024-01-29 14:03 ` [ruby-core:116477] " make_now_just (Hiroya Fujinami) via ruby-core
2024-01-29 23:14 ` [ruby-core:116487] " duerst via ruby-core
2024-03-20 23:19 ` [ruby-core:117271] " naruse (Yui NARUSE) via ruby-core
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-20095.20231227050827.53096@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=noreply@ruby-lang.org \
--cc=ruby-core@ml.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).