From: "jeremyevans0 (Jeremy Evans)" Date: 2021-11-04T14:36:03+00:00 Subject: [ruby-core:105938] [Ruby master Feature#18287] Support nil value for sort in Dir.glob Issue #18287 has been updated by jeremyevans0 (Jeremy Evans). Eregon (Benoit Daloze) wrote in #note-3: > This is inconsistent with basically every Ruby method out there. I disagree. It's not uncommon for me to do: ```ruby def m(opts={}) do_something unless opts[:something] == false # ... end ``` I think it is reasonable that a `nil` value is treated the same as not passing a value at all. ---------------------------------------- Feature #18287: Support nil value for sort in Dir.glob https://bugs.ruby-lang.org/issues/18287#change-94479 * Author: Strech (Sergey Fedorov) * Status: Open * Priority: Normal ---------------------------------------- Good day, everyone. I would like to suggest (or question) the support of a `nil` value for `sort` argument in `Dir.glob`. I find this behaviour a bit surprising, here is an example: ``` irb(main):001:0> Dir.glob("brace/a{.js,*}", sort: true) => ["brace/a.js", "brace/a", "brace/a.erb", "brace/a.html.erb", "brace/a.js", "brace/a.js.rjs"] irb(main):001:0> Dir.glob("brace/a{.js,*}", sort: false) => ["brace/a.js", "brace/a.js", "brace/a.html.erb", "brace/a.erb", "brace/a.js.rjs", "brace/a"] irb(main):001:0> Dir.glob("brace/a{.js,*}", sort: nil) => ["brace/a.js", "brace/a", "brace/a.erb", "brace/a.html.erb", "brace/a.js", "brace/a.js.rjs"] ``` As you can see ��� `sort: nil` produces the same results as `sort: true` which is confusing Github link: https://github.com/ruby/ruby/pull/5079 Ruby spec link: https://github.com/ruby/spec/pull/894 -- https://bugs.ruby-lang.org/ Unsubscribe: