[ruby-core:117770] [Ruby master Bug#20468] Segfault on safe navigation in for target
From:
"nobu (Nobuyoshi Nakada) via ruby-core" <ruby-core@...>
Date:
2024-05-04 08:49:41 UTC
List:
ruby-core #117770
Issue #20468 has been updated by nobu (Nobuyoshi Nakada). Assignee deleted (matz (Yukihiro Matsumoto)) I found that a `for` loop variable is looser than I expected. Not only a safe navigation call, even a constant can be used. I don't think a constant is useful as a loop variable that is expected to be re-assigned. https://github.com/ruby/ruby/pull/10723 ---------------------------------------- Bug #20468: Segfault on safe navigation in for target https://bugs.ruby-lang.org/issues/20468#change-108178 * Author: kddnewton (Kevin Newton) * Status: Open * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- ```ruby for foo&.bar in []; end ``` -- 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/