silver_phoenix (Pedro Pinto)
- Login: silver_phoenix
- Registered on: 07/04/2018
- Last sign in: 07/05/2018
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 1 | 1 |
Activity
07/05/2018
-
05:35 PM Ruby Bug #14895: Inconsistent constant names when using const_set on a singleton class
- So, what you're saying is that the singleton class is being assigned to a constant when it creates module `A`, so modules are only named after this step?
Is this expected behavior then? -
02:29 PM Ruby Bug #14895: Inconsistent constant names when using const_set on a singleton class
- Yes, I understand that, but why isn't `Z` named like `B` is?
`Z` is `#<Module:...>` (unnamed)
`B` is `#<...>::B` (named)
There's something not being initialized on the singleton class, which is only triggered after adding a named ...
07/04/2018
-
06:25 PM Ruby Bug #14895 (Closed): Inconsistent constant names when using const_set on a singleton class
- Constants defined in the namespace of a class or a module are named on the fly:
```ruby
class X; end
X.const_set(:Y, Module.new) # => X::Y
module M; end
M.const_set(:N, Module.new) # => M::N
```
Constants defined on a singleto...