rits (First Last)
- Login: rits
- Registered on: 11/04/2012
- Last sign in: 10/29/2014
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 0 | 0 |
Reported issues | 2 | 16 | 18 |
Activity
09/25/2014
- 04:52 PM Ruby master Bug #10142: named params don't always capture passed named args
- another example of how this creates surprise, confusion and subtle bugs
~~~ruby
def foo(a = 1, **options)
end
... - 01:44 AM Ruby master Bug #10293: splatting an empty hash in a method invocation sends an argument to the method (should send nothing)
- https://bugs.ruby-lang.org/issues/9291 is somewhat related
foo(**nil) should not raise since foo(*nil) does not and ...
09/24/2014
- 11:57 PM Ruby master Bug #10293 (Closed): splatting an empty hash in a method invocation sends an argument to the method (should send nothing)
- irb(main):001:0> def foo; end; foo **{}
ArgumentError: wrong number of arguments (1 for 0)
note that splatting an...
09/14/2014
- 04:43 AM Ruby master Feature #10177: Hash#has_key? and Hash#has_value? should be deprecated
- Tsuyoshi Sawada wrote:
> I don't understand how `has_key?` is better
I already explained it, all I can do is rest...
09/07/2014
- 08:33 PM Ruby master Feature #10177: Hash#has_key? and Hash#has_value? should be deprecated
- in the interest of maximizing the English readability and sensibility (self documentability) of predicates, it is key...
08/22/2014
- 04:00 PM Ruby master Bug #10142: named params don't always capture passed named args
- First Last wrote:
> Koichi Sasada wrote:
> > Sorry I missed this line.
> >
> > > in this specific example, key a...
08/17/2014
- 04:36 AM Ruby master Bug #10142: named params don't always capture passed named args
- Koichi Sasada wrote:
> Sorry I missed this line.
>
> > in this specific example, key arg b would be bound to key ... - 03:57 AM Ruby master Bug #10142: named params don't always capture passed named args
- Koichi Sasada wrote:
> (2014/08/16 12:49), meanlogin@gmail.com wrote:
> > this example is particularly illustrativ...
08/16/2014
- 03:49 AM Ruby master Bug #10142: named params don't always capture passed named args
- First Last wrote:
> Nobuyoshi Nakada wrote:
> > Mandatory arguments have priority over keywords arguments.
>
> i... - 03:45 AM Ruby master Bug #10142: named params don't always capture passed named args
- Nobuyoshi Nakada wrote:
> Mandatory arguments have priority over keywords arguments.
instead of just restating wh...
Also available in: Atom