[ruby-core:107021] [Ruby master Bug#18292] 3.1.0-dev `include` cause Module to be marked as initialized

Issue #18292 has been updated by byroot (Jean Boussier).


@jeremyevans thanks for the fix. Do you think we should mark this as a 3.1 backport?

----------------------------------------
Bug #18292: 3.1.0-dev `include` cause Module to be marked as initialized
https://bugs.ruby-lang.org/issues/18292#change-95854

* Author: byroot (Jean Boussier)
* Status: Closed
* Priority: Normal
* ruby -v: ruby 3.1.0dev (2021-11-08T09:35:22Z master 7cc4e147fc)
* Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN
----------------------------------------
Some subtle change I found while testing our app compatibility with Ruby head:

```ruby
class Mod1 < Module
  def initialize(...)
    super
  end
end
p Mod1.new

class Mod2 < Module
  def initialize(...)
    include Enumerable
    super
  end
end
p Mod2.new
```

On 3.0:
```
#<Mod1:0x00007fbf9b825b38>
#<Mod2:0x00007fbf9b825818>
```

On ruby-head:
```
#<Mod1:0x00000001108cb1d8>
/tmp/module.rb:11:in `initialize': already initialized module (TypeError)
	from /tmp/module.rb:11:in `initialize'
```

I suspect this might be a result of https://bugs.ruby-lang.org/issues/17048, but I have to admit I'm not certain so I'd rather report it.



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

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>