CppCon 2017: Bob Steagall “How to Write a Custom Allocator”

[@sicko815]

Watching this after John Lakos' talk Such a beautiful follow up

[@kinershah464]

Very good presentation. He must have done a lot of research and studying to compile the content for this presentation.

[@seidenada526]

Don't watch this talk if you are looking for some code examples. The subject is more like "What traits and types you should study in order to be able to write a custom allocator". Good material though.

[@cypix314123]

Yeah, it is more about what you need to define (in terms of traits) and how those definitions fit together. It is also a bit of history which could prove useful if you need to modernize allocators written by someone else.

[@Kalumbatsch]

Right, in that case you should watch the talk "Custom allocator code to cut & paste", this one is more about how to write a custom allocator.

[@seidenada526]

I prefer the talk of Andrei Alexandrescu in the CppCon 2015 about std :: allocator. Way more fun and teachful than your sarcasm.

[@Kalumbatsch]

Maybe, if "teachful" was a word.

[@fwang3695]

I love this man! thanks for these wonderful presentations!

[@s_alexander_n]

Thank you, Bob Steagall! 😃

[@tohopes]

20:10 deep propagation of alligators pretty scary!

[@pskocik]

it's what the reptilians want. they've deeply infiltrated c++ now.

[@lorenzombolis]

Anyone care to explain what the example at 11:00 is, or how it can be used? Because I have no clue whatsoever

[@IK-ow2zk]

Thanks a lot for the video!

[@CppCon]

Glad it was helpful!

[@jflopezfernandez]

Awesome talk, thank you

[@JohnForTheWin]

Great talk!

[@sproccoli]

i do not support alligator propagation. We have enough of them already.

[@КНЯЗЬДИМИТРИЙХВОРОСТИНИН]

Thank you! Спаси Господи!

[@anon_y_mousse]

Very informative, but Bob needs to incorporate some levity and differ the pitch of his voice from time to time. I nearly fell asleep.

[@pajeetsingh]

Why can't we just use new and delete again?

[@Theodorlei1]

The default stays new and delete :) Allocators allow you to open the hood and choose a different option if you need to

[@movax20h]

@Drip all of these can be solved with global allocator. Custom allocators are very niche and somehow over rated. Mostly useful to using stack as primary allocation with fallback, and for arena allocation. But even for that you don't need standard tools and can roll your own stuff for it, but if you try to use stl containers then you need to use them , or write an adapter.

[@dekadebashish]

@@movax20h they are still useful when you want to isolate the alloac and dealloc calls from the global allocator for some reason. (may be initial dev ). Also, for some library like json in c++, a developer might want to use some different allocator to improve performance.

[@alexeysubbota]

I stopped watching at half an hour because of lack of practical information about "How to write a custom allocator" at all.