From: nobu@... Date: 2018-01-11T08:20:52+00:00 Subject: [ruby-core:84827] [Ruby trunk Bug#14350] Strange behavior for Array.min in ruby 2.5.0 Issue #14350 has been updated by nobu (Nobuyoshi Nakada). `1` is not greater than `1.0`, and vice versa. The both results are correct in this case. But the previous behavior may be better in the case of `Numeric`-like objects. ---------------------------------------- Bug #14350: Strange behavior for Array.min in ruby 2.5.0 https://bugs.ruby-lang.org/issues/14350#change-69539 * Author: artofhuman (Semyon Pupkov) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: 2.5.0 * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- 2.4.2 ~~~ ruby [[1, 0.0].max, 1.0].min => 1 ~~~ 2.5.0 ~~~ ruby [[1, 0.0].max, 1.0].min => 1.0 [[1, 0.0].max, 1.0] => [1, 1.0] [1, 1.0].min => 1 ~~~ I think it`s regression for ruby 2.5.0 -- https://bugs.ruby-lang.org/ Unsubscribe: