Project

General

Profile

Actions
Copy link

Bug #17857

closed

`when 0r` and `when 0i` do not match with `case 0`

Added by mame (Yusuke Endoh) over 3 years ago. Updated over 3 years ago.

Status:
Closed
Assignee:
-
Target version:
-
ruby -v:
Backport:
2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN
[ruby-core:103791]

Description

The following code prints :bar between Ruby 2.1 .. 2.5, and dumps core since Ruby 2.6.

case 0
when 0r
  p :foo
else
  p :bar #=> :bar
end

A Complex has the same issue.

case 0
when 0i
  p :foo
else
  p :bar #=> :bar
end

The segfault issue was fixed by #17854. So the current master it prints :bar.

However, I believe it should print :foo because 0r === 0 evaluates to true. This weird behavior is caused by the optimization which uses a hidden hash to dispatch to when clauses. By disabling the optimization, the code prints :foo.

opt = RubyVM::InstructionSequence.compile_option
opt[:specialized_instruction] = false
RubyVM::InstructionSequence.compile(<<END, **opt).eval
case 0
when 0r
  p :foo #=> :foo
else
  p :bar
end
END

I think the optimization should be disabled when T_RATIONAL or T_COMPLEX are used.

Related issues 1 (0 open — 1 closed)

Related to Ruby master - Bug #17854: Crash with certain "case" expressions on FreeBSDClosedshyouhei (Shyouhei Urabe)Actions
Actions
Copy link

Also available in: Atom PDF

Like0
Like0Like0Like0Like0