CppCon 2017: John Lakos “Local ('Arena') Memory Allocators (part 1 of 2)”

[@simonfarre4907]

This is probably one of the best talks ever given at CppCon.

[@Omnicypher001]

@39:36 lol

[@niles_5003]

I sincerely hope this man is a professor somewhere. He's an amazing lecturer and definitely someone you want to learn a lot from. I like how he keeps people engaged, manages the room, and even made me laugh out loud all while covering some pretty technical material that's mostly new to me.

[@abhishekk4194]

The clarity blew me away.

[@АлександрДаас]

Thank you, great talk

[@CppCon]

Glad you enjoyed it!

[@azdinator]

Oh man. That guy is really good. Thank you.

[@IllumTheMessage]

Excellent talk.

[@unevaguejaune8671]

34:25 Can someone explain me what the problem / purpose of the inline specifier is ? Or what he is trying to show ?

[@SalokinX]

He wants to highlight the fact that the function definitions are meant to be Inline and that he didn't inline them (by defining the function in the class definition) just so it's easier to see on the slide.

[@tomcheng3903]

The functions are inlined by default, so there's no need for the inline keyword - the compiler will error if you try to insert an extraneous 'inline', since it's not possible to have a non-inline allocator.

[@Jimmy9Bazooka]

@@tomcheng3903 Nope. He's lying. You can have extra 'inline' specifier on an inline class function. There will be no error.

[@LordNezghul]

Talking "this is very important" should be at the end of part 2 not because "you said so/I am here" but because people already saw this is important.

[@TimothyJesionowski]

Excellent presentation, very educational while being somehow entertaining. As a C fanboy this is one of the few c++ features I genuinely want, though I'm sure I can kind of get it with stateful functions.

[@robbydomino]

great talk

[@andik70]

"we meaning me" :-)

[@PflanzenChirurg]

What a fucking GEM

[@hmpcon]

Lakos's talks are always a stream of consciousness :P

[@xr.spedtech]

This guy is cool

[@matveyshishov]

Pure joy! ❤

[@yb9737]

GREAT TALK

[@marinrusu9179]

23:37

[@sampathsubasinghe929]

49:58 How to determine allocation density is low for billion integers when reserved memory or capacity() is not given.

[@rastaarmando7058]

On my machine vector allocates (1.5 * sizeOfCurrentMemory) each time it runs out of space. should be similar on yours so, I guess u could use that?

[@rocknroooollllll]

Death by powerpoint, John. Every. Single. Time. You have great talent, but massive information overload.

[@prateekpatil4845]

I love it.

[@PflanzenChirurg]

@@prateekpatil4845 me too ^^

[@zokalyx]

just a long presentation imo, not overloaded

[@mrlithium69]

@56:00 How has he not heard #pragma pack(push, 1). You put it around a specific struct, and disable it after w/ #pragma pack(pop)

[@dyslexicunt]

Yeah it's always reassuring when someone deemed fit to give a presentation on custom allocators, is completely ignorant of a basic compiler feature dealing with memory alignment. Way to go.

[@ciaran2679]

I'd imagine it's because this is a talk about standard C++, not compiler-specific extensions.

[@eggdish]

I understand not knowing about a non standard pragma and personally I don't like the pragma anyway. However, the speaker is clearly misinformed about unaligned data hurting performance, or is programming in non-x86 environment. Google "lemire unaligned x86" for nice blog post with benchmarks. (Might not apply to floating point)

[@Bozemoto]

Useful for stuff like loading binary file headers like BMP and WAV though.

[@andreyblack2558]

you just a stupid fool if your think what hi has newer heard about it, its a trick

[@MsDuketown]

arena.h needs a forum.h Otherwize, floating atomics will extinguish humanity.