From: "Eregon (Benoit Daloze)" <noreply@...>
Date: 2022-06-17T09:49:30+00:00
Subject: [ruby-core:108977] [Ruby master Bug#18832] Suspicious superclass mismatch

Issue #18832 has been updated by Eregon (Benoit Daloze).


@fxn Yes, but that is too long. What I think is useful for the dev meeting is a snippet of a few lines, which represents and reproduces the real issue.
e.g. I find all the examples with M/C above too synthetic and hard to judge if it matters.

----------------------------------------
Bug #18832: Suspicious superclass mismatch
https://bugs.ruby-lang.org/issues/18832#change-98082

* Author: fxn (Xavier Noria)
* Status: Open
* Priority: Normal
* Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
The following code:

```ruby
module M
  class C
  end
end

include M

p Object.const_defined?(:C, false)

class C < String # (1)
end
```

prints `false`, as expected, but then raises `superclass mismatch for class C (TypeError)` at (1).

I believe this is a bug, because `Object` itself does not have a `C` constant, so (1) should just work, and the superclasse of `M::C` should be irrelevant.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>