Project

General

Profile

Actions
Copy link

Bug #19548

closed

Ambiguous and confusing syntax for alias/undef arguments

Added by hurricup (Alexandr Evstigneev) about 2 years ago. Updated about 2 years ago.

Status:
Rejected
Assignee:
-
Target version:
-
ruby -v:
Backport:
2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN
[ruby-core:113022]

Description

This was introduced in https://bugs.ruby-lang.org/issues/8851 and looks really confusing at least because of bare /.
Here are 3 semantically similar methods, but feels like first two should not be valid:

def method1
  undef :*,<<,/,[]
  alias :* /
end

def method2
  undef :*,
    <<,
    /,
    []
  alias :*
  /
end

def method3
  undef :*
  undef :<<
  undef :/
  undef :[]
  alias :* :/
end

puts RubyVM::InstructionSequence.of(method :method1).disasm
puts RubyVM::InstructionSequence.of(method :method2).disasm
puts RubyVM::InstructionSequence.of(method :method3).disasm
Actions
Copy link
 #1 [ruby-core:113091]

Updated by jeremyevans0 (Jeremy Evans) about 2 years ago

  • Status changed from Open to Rejected

This isn't a bug, nor does it appear to be introduced by #8851 (that added support for %s symbol literals with alias/undef, other symbol literals were already supported). undef and alias have always accepted symbols and bare words, so alias :* / and undef :*, / work, as do alias * / and undef *, /. Not allowing bare words would break existing code.

Actions
Copy link

Also available in: Atom PDF

Like0
Like0