Issue #14748 has been reported by nelhage (Nelson Elhage).

----------------------------------------
Bug #14748: Inconsistent (and regressed from 2.4) behavior on `Array#min` and max between array literals and arrays
https://bugs.ruby-lang.org/issues/14748

* Author: nelhage (Nelson Elhage)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin17]
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
`Array#min` and `Array#max` have different behavior depending on whether or not they are called with array literals:


~~~
$ ruby -e 'puts([1.0, 1].min); one_f = 1.0; one = 1; puts([one_f, one].min)'
1.0
1
~~~

This is a regression from 2.4, where both forms would return `1.0`.

I believe this to be a bug introduced by https://bugs.ruby-lang.org/issues/12172 -- disassembly reveals that only the second form uses `opt_newarray_min`



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>