[#71439] [Ruby trunk - Feature #11339] [PATCH] io.c: avoid kwarg parsing in C API — matz@...
Issue #11339 has been updated by Yukihiro Matsumoto.
7 messages
2015/11/11
[#71473] Re: [Ruby trunk - Feature #11339] [PATCH] io.c: avoid kwarg parsing in C API
— Eric Wong <normalperson@...>
2015/11/13
Entire series for sockets
[#71450] Ruby 2.3.0-preview1 Released — "NARUSE, Yui" <naruse@...>
Hi,
5 messages
2015/11/11
[#71617] [Ruby trunk - Feature #11664] [PATCH] introduce rb_autoload_value to replace rb_autoload — nobu@...
Issue #11664 has been updated by Nobuyoshi Nakada.
3 messages
2015/11/20
[#71721] [Ruby trunk - Feature #11741] Migrate Ruby to Git from Subversion — me@...
Issue #11741 has been updated by Jon Moss.
4 messages
2015/11/28
[ruby-core:71532] [Ruby trunk - Bug #11705] [Open] Namespace resolution in nested modules with short syntax
From:
mike@...
Date:
2015-11-17 23:28:36 UTC
List:
ruby-core #71532
Issue #11705 has been reported by Mike Pastore.
----------------------------------------
Bug #11705: Namespace resolution in nested modules with short syntax
https://bugs.ruby-lang.org/issues/11705
* Author: Mike Pastore
* Status: Open
* Priority: Normal
* Assignee:
* ruby -v:
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
Given the following definition:
~~~
module Foo
class Qux
def self.hello
'Hello, world!'
end
end
end
~~~
Namespace resolution at a later time works differently when you have nested modules, e.g.
~~~
module Foo
module Bar
# Can't find Foo::Bar::Qux, so "goes up" to find Foo::Qux.
p Qux.hello # < "Hello, world!"
end
end
~~~
vs. the short syntax, e.g.
~~~
module Foo::Bar
# Can't find Foo::Bar::Qux, but doesn't "go up" to find Foo::Qux.
p Qux.hello # < in `<module:Bar>': uninitialized constant Foo::Bar::Qux (NameError)
end
~~~
Is this intentional and/or expected?
--
https://bugs.ruby-lang.org/