Issue #20056 has been updated by jeremyevans0 (Jeremy Evans). zverok (Victor Shepelev) wrote:

1. There is no block form for `Dir#chdir`, unlike `Dir.chdir` (the form that will return to the previous directory when the block is finished)

`Dir#chdir` implicitly calls `Dir.chdir` or `Dir.fchdir` with the passed block, so the block form does work, but it apparently is not documented: ```ruby p Dir.pwd # => '/home/jeremy' Dir.new('..').chdir{p Dir.pwd} # => '/home' p Dir.pwd # => '/home/jeremy' ```

2. `Dir.chdir` returns `0`, while `Dir#chdir` returns `nil` (both seem to be not representing any particular internal value, just a hardcoded return value).

Return value being `nil` is expected. I assume the only reason `Dir.chdir` returns `0` is backwards compatibility, as I highly doubt we would use `0` as the return value for success for new methods. ---------------------------------------- Misc #20056: Dir#chdir inconsistency with Dir.chdir https://bugs.ruby-lang.org/issues/20056#change-105617 * Author: zverok (Victor Shepelev) * Status: Open * Priority: Normal * Assignee: jeremyevans0 (Jeremy Evans) ---------------------------------------- I am not sure it is important; I just wanted to understand if this is intentional or accidental. 1. There is no block form for `Dir#chdir`, unlike `Dir.chdir` (the form that will return to the previous directory when the block is finished) 2. `Dir.chdir` returns `0`, while `Dir#chdir` returns `nil` (both seem to be not representing any particular internal value, just a hardcoded return value). -- https://bugs.ruby-lang.org/

Issue #20056 has been updated by zverok (Victor Shepelev). Status changed from Closed to Open Actually, I found _another_ inconsistency while writing docs. Not sure it is worth fixing, but still somewhat confusing: ```ruby Dir.chdir('doc') do |*args| p args #=> ["doc"] "res" end.tap { p _1 } #=> "res" Dir.new('doc').chdir do |*args| p args #=> [] "res" end.tap { p _1 } #=> nil Dir.fchdir(Dir.new('doc').fileno) do |*args| p args #=> [] "res" end.tap { p _1 } #=> "res" ``` The difference in args passing into a block might cause only mild confusion, but the fact that the `Dir#chdir` doesn't return the block result seems problematic. Unless I am missing something again. ---------------------------------------- Misc #20056: Dir#chdir inconsistency with Dir.chdir https://bugs.ruby-lang.org/issues/20056#change-105629 * Author: zverok (Victor Shepelev) * Status: Open * Priority: Normal * Assignee: jeremyevans0 (Jeremy Evans) ---------------------------------------- I am not sure it is important; I just wanted to understand if this is intentional or accidental. 1. There is no block form for `Dir#chdir`, unlike `Dir.chdir` (the form that will return to the previous directory when the block is finished) 2. `Dir.chdir` returns `0`, while `Dir#chdir` returns `nil` (both seem to be not representing any particular internal value, just a hardcoded return value). -- https://bugs.ruby-lang.org/

Issue #20056 has been updated by zverok (Victor Shepelev).

Not passing an argument to the block in the Dir.fchdir or Dir#chdir case makes sense to me.

Yup, I can see the reasoning, that's why I don't think it is a big problem. (I thought that may be passing `self`, i.e. an instance of `Dir` inside the block might be a good idea, but the implementation doesn't allow that.) On the other hand, the return value of the block in `#chdir` case should be fixed, don't you think? I think this should do, probably... ```diff dir_chdir(VALUE dir) { #if defined(HAVE_FCHDIR) && defined(HAVE_DIRFD) && HAVE_FCHDIR && HAVE_DIRFD - dir_s_fchdir(rb_cDir, dir_fileno(dir)); + return dir_s_fchdir(rb_cDir, dir_fileno(dir)); #else VALUE path = dir_get(dir)->path; - dir_s_chdir(1, &path, rb_cDir); + return dir_s_chdir(1, &path, rb_cDir); #endif - - return Qnil; } ``` ---------------------------------------- Misc #20056: Dir#chdir inconsistency with Dir.chdir https://bugs.ruby-lang.org/issues/20056#change-105632 * Author: zverok (Victor Shepelev) * Status: Open * Priority: Normal * Assignee: jeremyevans0 (Jeremy Evans) ---------------------------------------- I am not sure it is important; I just wanted to understand if this is intentional or accidental. 1. There is no block form for `Dir#chdir`, unlike `Dir.chdir` (the form that will return to the previous directory when the block is finished) 2. `Dir.chdir` returns `0`, while `Dir#chdir` returns `nil` (both seem to be not representing any particular internal value, just a hardcoded return value). -- https://bugs.ruby-lang.org/

Issue #20056 has been updated by zverok (Victor Shepelev).

That's more or less the same diff I came up with before I determined we need more refactoring so that `Dir#chdir` never yields an argument to the block.

I provided the diff to solve return value problem for the **block form**. Which is not a _big_ problem, but still might be confusing: ```ruby Dir.chdir('doc') do # ...some more logic or calling other modules # ...which might do something like... Dir['*.md'].map { File.read(_1) }.join("\n\n") end #=> what was calculated in the block Dir.new('doc').chdir do Dir['*.md'].map { File.read(_1) }.join("\n\n") end #=> nil ``` This is simply fixed by `return`ing what the called method have returned, right? Whatever the implementation is chosen. ---------------------------------------- Misc #20056: Dir#chdir inconsistency with Dir.chdir https://bugs.ruby-lang.org/issues/20056#change-105635 * Author: zverok (Victor Shepelev) * Status: Open * Priority: Normal * Assignee: jeremyevans0 (Jeremy Evans) ---------------------------------------- I am not sure it is important; I just wanted to understand if this is intentional or accidental. 1. There is no block form for `Dir#chdir`, unlike `Dir.chdir` (the form that will return to the previous directory when the block is finished) 2. `Dir.chdir` returns `0`, while `Dir#chdir` returns `nil` (both seem to be not representing any particular internal value, just a hardcoded return value). -- https://bugs.ruby-lang.org/

Issue #20056 has been updated by zverok (Victor Shepelev).

It does fix the block return value, but doesn't fix the Dir#chdir block yielding the path if fchdir is not supported.

I understand that. But for now, just fixing the return value (while ignoring args inconsistency) before 3.3 seems more reasonable than not fixing it? Or do you plan the deeper refactoring soon? ---------------------------------------- Misc #20056: Dir#chdir inconsistency with Dir.chdir https://bugs.ruby-lang.org/issues/20056#change-105637 * Author: zverok (Victor Shepelev) * Status: Open * Priority: Normal * Assignee: jeremyevans0 (Jeremy Evans) ---------------------------------------- I am not sure it is important; I just wanted to understand if this is intentional or accidental. 1. There is no block form for `Dir#chdir`, unlike `Dir.chdir` (the form that will return to the previous directory when the block is finished) 2. `Dir.chdir` returns `0`, while `Dir#chdir` returns `nil` (both seem to be not representing any particular internal value, just a hardcoded return value). -- https://bugs.ruby-lang.org/

Issue #20056 has been updated by jeremyevans0 (Jeremy Evans). Tracker changed from Misc to Bug Status changed from Open to Closed Backport set to 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN Fixed by commit:f49af3c969eb7ba9937514a229b49e5b7d91f0f1 ---------------------------------------- Bug #20056: Dir#chdir inconsistency with Dir.chdir https://bugs.ruby-lang.org/issues/20056#change-105647 * Author: zverok (Victor Shepelev) * Status: Closed * Priority: Normal * Assignee: jeremyevans0 (Jeremy Evans) * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- I am not sure it is important; I just wanted to understand if this is intentional or accidental. 1. There is no block form for `Dir#chdir`, unlike `Dir.chdir` (the form that will return to the previous directory when the block is finished) 2. `Dir.chdir` returns `0`, while `Dir#chdir` returns `nil` (both seem to be not representing any particular internal value, just a hardcoded return value). -- https://bugs.ruby-lang.org/