Xavier Noria

  • Email:
  • Registered on: 03/21/2010
  • Last connection: 02/04/2014

Activity

Reported issues: 1

12/07/2013

01:57 AM ruby-trunk Feature #9123: Make Numeric#nonzero? behavior consistent with Numeric#zero?
@Guilherme
A predicate in Ruby can return any object. If the exact return value is documented, then the user of the ...

11/19/2013

08:49 PM ruby-trunk Feature #9123: Make Numeric#nonzero? behavior consistent with Numeric#zero?
This ticket is not about changing the semantics of the Ruby language. It is a ticket about a particular predicate.
C...
03:39 AM ruby-trunk Feature #9123: Make Numeric#nonzero? behavior consistent with Numeric#zero?
I wouldn't care. I use predicates as predicates
do_foo if x.zero?
also
do_bar if str =~ /.../
the =~ oper...
03:23 AM ruby-trunk Feature #9123: Make Numeric#nonzero? behavior consistent with Numeric#zero?
Both predicates return a boolean value, whose exact nature is irrelevant. I see no inconsistency to fix.
In my vie...

08/05/2012

08:51 PM ruby-trunk Feature #5478: import Set into core, add syntax
I don't know which is the general position of core with respect to non-ASCII in source code, but the natural literal ...

07/29/2012

11:49 PM ruby-trunk Feature #6810: `module A::B; end` is not equivalent to `module A; module B; end; end` with respec...
Perry, totally agreed. The way this works and how constant name resolution works should be a well-covered topic. But ...
09:38 PM ruby-trunk Feature #6810: `module A::B; end` is not equivalent to `module A; module B; end; end` with respec...
They are very decoupled, name is the only bit mostly in common, set on constant assignment. May I link to a talk of m...
05:09 AM ruby-trunk Feature #6810: `module A::B; end` is not equivalent to `module A; module B; end; end` with respec...
I cannot tell you the ultimate rationale behind this, but I can tell you that with the current semantics that is not ...
04:10 AM ruby-trunk Feature #6810: `module A::B; end` is not equivalent to `module A; module B; end; end` with respec...
Yes, this is expected.
The resolution algorithm first checks the modules in the nesting (in their very constants tab...

07/14/2012

08:51 PM ruby-trunk Bug #5887: The documentation of Module.constants is incorrect
I think this description could be better.
On one hand I find a little surprising that the first sentence mentions ...

Also available in: Atom