Project

General

Profile

Actions

Bug #17745

open

`IO#close_on_exec=` returns different value when called with `send, __send__, public_send` or not

Added by kachick (Kenichi Kamiya) about 2 months ago. Updated about 2 months ago.

Status:
Open
Priority:
Normal
Assignee:
-
Target version:
-
ruby -v:
ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-darwin20]
[ruby-core:102998]

Description

$ ruby -v -e 'p(STDIN.close_on_exec = 42)'
ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-darwin20]
42
$ ruby -v -e 'p(STDIN.__send__ :close_on_exec=, 42)'
ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-darwin20]
nil

Is this an intentional behavior?
ruby/spec has the test case, But I can't think any benefit this different returning value 🤔

PR: https://github.com/ruby/ruby/pull/4321

Updated by Eregon (Benoit Daloze) about 2 months ago

The PR looks good to me.

As you may know recv.foo= value always return value, no matter what the foo= method returns.
So in general the return value of assignment methods might differ and is probably best to be ignored.

Updated by nobu (Nobuyoshi Nakada) about 2 months ago

I also think the "returns nil" example should be removed simply.

Actions

Also available in: Atom PDF