[#98645] [Ruby master Misc#16933] DevelopersMeeting20200618Japan — mame@...

Issue #16933 has been reported by mame (Yusuke Endoh).

14 messages 2020/06/04

[#98663] [Ruby master Bug#16936] `make check TESTS="-n !/Foo#method/"` not skipping the test case — jaruga@...

Issue #16936 has been reported by jaruga (Jun Aruga).

13 messages 2020/06/05

[#98772] [Ruby master Bug#16959] Weakmap has specs and third-party usage despite being a private API — headius@...

Issue #16959 has been reported by headius (Charles Nutter).

13 messages 2020/06/12

[#98826] [Ruby master Feature#16963] Remove English.rb from Ruby 2.8/3.0 — hsbt@...

Issue #16963 has been reported by hsbt (Hiroshi SHIBATA).

9 messages 2020/06/16

[#98920] [Ruby master Bug#16978] Ruby should not use realpath for __FILE__ — v.ondruch@...

Issue #16978 has been reported by vo.x (Vit Ondruch).

24 messages 2020/06/23

[#98947] [Ruby master Feature#16986] Anonymous Struct literal — ko1@...

Issue #16986 has been reported by ko1 (Koichi Sasada).

66 messages 2020/06/26

[#98964] [Ruby master Feature#16989] Sets: need ♥️ — marcandre-ruby-core@...

Issue #16989 has been reported by marcandre (Marc-Andre Lafortune).

33 messages 2020/06/26

[#98965] [Ruby master Feature#16990] Sets: operators compatibility with Array — marcandre-ruby-core@...

Issue #16990 has been reported by marcandre (Marc-Andre Lafortune).

11 messages 2020/06/26

[#98968] [Ruby master Feature#16993] Sets: from hash keys using Hash#key_set — marcandre-ruby-core@...

Issue #16993 has been reported by marcandre (Marc-Andre Lafortune).

10 messages 2020/06/26

[#98997] [Ruby master Feature#17000] 2.7.2 turns off deprecation warnings by deafult — mame@...

Issue #17000 has been reported by mame (Yusuke Endoh).

16 messages 2020/06/30

[ruby-core:98843] [Ruby master Bug#16966] Unexpected behavior of sort method

From: mame@...
Date: 2020-06-17 23:49:34 UTC
List: ruby-core #98843
Issue #16966 has been updated by mame (Yusuke Endoh).

Status changed from Open to Rejected

It is a bug of the book.  Please report it to the author :-)

There is no guarantee about which `x` or `y` accepts each element.  The following code will work as expected.

```
[1,100,42,23,26,1000].sort {|x,y| x==42 ? 1 : y==42 ? -1 : x<=>y } #=> [1, 23, 26, 100, 1000, 42]
```

----------------------------------------
Bug #16966: Unexpected behavior of sort method
https://bugs.ruby-lang.org/issues/16966#change-86206

* Author: kk (Kirill /)
* Status: Rejected
* Priority: Normal
* ruby -v: 2.7.0
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
Hey there

I've been going through the old ruby cook book from 2015 which uses ruby 2.1.

It has the following example of using sort method

``` ruby
[1,100,42,23,26,1000].sort {|x,y| x==42 ? 1 : x<=>y }
```
 

It's supposed to return `[1, 23, 26, 100, 10000, 42]`

-
So, I tried this with ruby 2.7.0 and it returned `[1, 23, 26, 42, 100, 1000]`

Same story with 2.6.5


-
If we try a different array `[1,2,42,46,22,33].sort {|x,y| x==42 ? 1 : x<=>y }`  It'll return  `[1, 2, 22, 33, 46, 42]` as expected with 42 at the end.

---Files--------------------------------
Screenshot 2020-06-16 at 15.09.41.png (151 KB)


-- 
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>

In This Thread

Prev Next