You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thanks for bringing this up! I believe what C++ Insights shows is correct. We can have both a static and non-static version. It is up to us to say when the operator should be static. See cppreference.com/w/cpp/memory/new/operator_new
... Both single-object and array allocation functions may be defined as public static member functions of a class (versions (15-18)). ...
my appologies but my initial answer was wrong. You're right, the overloaded operators new and delete are implicitly static. Here is the correct source: [class.free]
Shouldn't the generated output prefix the keyword 'static' in member function as operator new and delete functions are static by default?
operator new and delete
The text was updated successfully, but these errors were encountered: