From: "jeremyevans0 (Jeremy Evans) via ruby-core" <ruby-core@...>
Date: 2024-03-01T00:35:59+00:00
Subject: [ruby-core:117019] [Ruby master Feature#20317] Removing the `allocate` method should cause `new` to fail

Issue #20317 has been updated by jeremyevans0 (Jeremy Evans).


The current behavior may be what you want if you want to ensure that new instances of the class have `#initialize` called on them.  I suppose you could switch to making `allocate` private, but that still would allow for `send(:allocate)`.

If we disallow `.new` if `.allocate` is undefined, should we also disallow `#dup` and `#clone`, both of which also need to allocate an object?

----------------------------------------
Feature #20317: Removing the `allocate` method should cause `new` to fail
https://bugs.ruby-lang.org/issues/20317#change-107082

* Author: tenderlovemaking (Aaron Patterson)
* Status: Open
----------------------------------------
When you remove the `allocate` method from a class the you can't allocate the class via the `allocate` method. However, you _can_ allocate the class via the `new` method:

```ruby
class Foo; end

Foo.singleton_class.undef_method(:allocate)

begin
  Foo.allocate # doesn't work, of course
rescue NoMethodError
end

begin
  Class.instance_method(:allocate).bind_call(Foo) # also doesn't work
rescue TypeError
end

Foo.new # works?
```

I think that when we remove the `allocate` method, the `new` method should also fail as there is no `allocate` method for `new` to call.



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/