[ruby-core:96228] [Ruby master Feature#16419] FrozenError.new ignores receiver:

[email protected]
Newsgroups gmane.comp.lang.ruby.core
Message-ID <redmine.journal-83121.20191214085347.372bcdb1f3a0f03b@ruby-lang.org>
Issue #16419 has been updated by jeremyevans0 (Jeremy Evans).


Whether to use a positional argument or a keyword argument was discussed in #15751.  I don't have a strong feelings either way (one of the patches I added in #15751 supported keyword arguments), and I don't think @eregon or @nobu had strong feelings either.  If you are strongly in favor of switching to a keyword argument, please commit the change. I'll probably not be in a position to commit anything until December 20.

----------------------------------------
Feature #16419: FrozenError.new ignores receiver:
https://bugs.ruby-lang.org/issues/16419#change-83121

* Author: znz (Kazuhiro NISHIYAMA)
* Status: Open
* Priority: Normal
* Assignee: jeremyevans0 (Jeremy Evans)
* Target version: 
----------------------------------------
Other exception classes with receiver accept recevier as keyword argument of new.
But FrozenError.new accept as positional argument.
I think keyword argument is better consistency.

```
% git grep 'receiver[:=]' ../error.c
../error.c: *   FrozenError.new(msg=nil, receiver=nil)  -> name_error
../error.c: *   NameError.new(msg=nil, name=nil, receiver: nil)  -> name_error
../error.c: *    [1, 2, 3].method(:rject) # NameError with name "rject" and receiver: Array
../error.c: *    [1, 2, 3].singleton_method(:rject) # NameError with name "rject" and receiver: [1, 2, 3]
../error.c: *   NoMethodError.new(msg=nil, name=nil, args=nil, private=false, receiver: nil)  -> no_method_error
../error.c: *   KeyError.new(message=nil, receiver: nil, key: nil) -> key_error
```



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.