C++ Cache Friendly Data + Functional + Ranges = ❤️ - Björn Fahller - C++ on Sea 2024

[@N....]

It's always quite interesting when using better abstractions causes the compiler to generate better code.

[@AlfredoCorrea]

25:57 41:40 At various points of the presentation the speaker confuses value_type with reference_type, perhaps it is a slip of the tongue and an effect of the slideware. But, if it is intentional, I think this confusion can have important negative ramifications in the design and usability of the library. The point is that a tuple of references (tuple)is not a good value_type, but it can be a good reference_type. the value_type should be tuple. Great talk!

[@Voy2378]

at 10:37 wont his structured binding do 4 mem accesses although he only needs z, or we rely on compiler to optimize that away since only z is needed? edit: nvm, he talks about it later

[@Voy2378]

Cool talk, would be nice if he did benchmarks in the slides, not live, it breaks the flow... Also would be nice if he did some benchmark with count_if, 100 columns, 2 selected and show how much faster is it than count_if on array of structures

[@adamrushford]

it's twice as fast.. fuck production this is going in my engine

[@BrunoBeltran]

Why not just use an in memory DB here? DuckDB I'm sure would at least be faster and better than anything I would write 🙈

[@mytech6779]

r/whooosh This is for the people writing such a data structure not about the end user of the data.

[@AlfredoCorrea]

Well, the idea is to have a native C++ solution I guess, not something that needs to *talk* to a database however efficient the database might be in itself.

[@karolyhorvath7624]

@BrunoBeltran: Then I guess you shouldn't program in C++