Overloading new (for the purpose, of e.g. adding a thread-local allocator) adds ... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		heavenlyblue on Dec 24, 2018 \| parent \| context \| favorite \| on: I disagree with Linus Torvalds about C++ (2009) Overloading new (for the purpose, of e.g. adding a thread-local allocator) adds implicit global state that isn't always easy to manage.

gpderetta on Dec 24, 2018 | [–]

Sure, but no more than the standard allocator. Explicit allocator objects are a superior solution most of the time anyway.

martinlaz on Dec 25, 2018 | [–]

Good memory management is never easy on a system level, so if one is overloading new, they'd better be comfortable around the complexities involved.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact