Issue #17004 has been updated by headius (Charles Nutter).


In `rb_whether_the_return_value_is_used_p` I believe `whether_the` is redundant with `p`. `is` also seems unnecessary here, so perhaps `rb_return_vaue_used` and `return_value_used?` are good enough?

There is a possible concern if this is used for values that have visible side effects (changing some internal state, setting `$~` or `$_`, possibly raising an exception, ...), so it should be used very carefully. Return value may not be the only effect that's important.

----------------------------------------
Feature #17004: Provide a way for methods to omit their return value
https://bugs.ruby-lang.org/issues/17004#change-86380

* Author: shyouhei (Shyouhei Urabe)
* Status: Open
* Priority: Normal
----------------------------------------
In ruby, it often is the case for a method's return value to not be used by its caller.  Even when a method returns something meaningful, its caller is free to ignore it.

Why not provide a way for a method to know if its return value is needed or not?  That adds a room for methods to be optimized, by for instance skipping creation of complex return values.

The following pull request implements `RubyVM.return_value_is_used?` method, which does that: https://github.com/ruby/ruby/pull/3271



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