Ruby Issue Tracking System

12/21/2019

04:52 PM Ruby Feature #6810: `module A::B; end` is not equivalent to `module A; module B; end; end` with respect to constant lookup (scope)

I just inadvertently made a dup of this issue (#16430) and would like to throw my hat in the ring as supporting this change.
Honestly, this literally the first time since I started ruby that I encountered something in the language th... MikeVastola (Mike Vastola)

01:45 PM Ruby Feature #16430: Resultion of constants in enclosing class/module affected by how nested classes/modules are declared

mame (Yusuke Endoh) wrote:
> If you want to request a feature, please research the old tickets. I've found #6810.
Ok, thanks. I tried searching before submitting this, but I apparently didn't use the right terms. MikeVastola (Mike Vastola)

02:27 AM Ruby Feature #16430: Resultion of constants in enclosing class/module affected by how nested classes/modules are declared

Fixed small bug in initial description. MikeVastola (Mike Vastola)

02:25 AM Ruby Feature #16430: Resultion of constants in enclosing class/module affected by how nested classes/modules are declared

sawa (Tsuyoshi Sawada) wrote:
> What is the purpose of writing the code in three different files? It only looks to me that it is making things more complicated.
I was trying to offer a minimal (non)-working example. The benefit arise... MikeVastola (Mike Vastola)

02:23 AM Ruby Feature #16430: Resultion of constants in enclosing class/module affected by how nested classes/modules are declared

mame (Yusuke Endoh) wrote:
> It is by design. See "Scope" section of https://github.com/ruby/ruby/blob/master/doc/syntax/modules_and_classes.rdoc
Ok, I see that, but is this a good design? I would argue not and am therefore changing... MikeVastola (Mike Vastola)

12/17/2019

08:13 PM Ruby Feature #16430 (Rejected): Resultion of constants in enclosing class/module affected by how nested classes/modules are declared

I'm not sure if this is intentional (in which case it really isn't documented anywhere, and probably should be) or a bug, but imagine the following code:
``` ruby
# lib/a.rb
module A
FOO = :BAR
end
# lib/a/b.rb
require_relat... MikeVastola (Mike Vastola)

11/22/2018

05:51 PM Ruby Feature #11689: Add methods allow us to get visibility from Method and UnboundMethod object.

I mean, as seen in yui-knk's example with `pry`, I think it's helpful to be able to essentially do `send("#{method.visibility}_instance_methods")`. I'm not picky on the name though if there is something better than visibility.
But I t... MikeVastola (Mike Vastola)

11/05/2018

12:40 AM Ruby Feature #11689: Add methods allow us to get visibility from Method and UnboundMethod object.

Oh, sorry. I missed where you were looking for an example before. Here's a good one from the popular activesupport gem: [here](https://github.com/rails/rails/blob/c823f9252be2552c65bb1370ccf42a14de461439/activesupport/lib/active_support/... MikeVastola (Mike Vastola)

10/22/2018

09:42 PM Ruby Feature #11689: Add methods allow us to get visibility from Method and UnboundMethod object.

Just wanted to second this FR as something I'd find useful.
Also, it would be nice to have associated predicate methods (i.e. `Method#public?`, `Method#protected?` and `Method#private?`)
MikeVastola (Mike Vastola)

12/24/2016

05:25 AM Ruby Feature #12979: Avoid exception for #dup on Integer (and similar cases)

Sorry.. I'm not used to Redmine and I was confused because there was no conclusion to the discussion about the **`ArgumentError`**.
I understand that Casper's request should be a separate issue (I'll leave him to submit that since I ... MikeVastola (Mike Vastola)