> Is boost::multi_index_container no longer a thing? Depends on the shop. I haven't seen one in production so far, but I don't doubt some people use it. > Als

> Is boost::multi_index_container no longer a thing? Depends on the shop. I haven't seen one in production so far, but I don't doubt some people use it. > Also there's SQLite with the :memory: database. Ah, now that's cheating. I know, because I did that too. I did that because of the realization that half the members I'm stuffing into classes to store my game state are effectively poor man's hand-rolled tables, indices and spatial indices, so why not just use a proper database for this?. > And this ancient 4gl we use at work has in-memory tables (as in database tables, with typed columns and any number of unique or not indexes) as a basic language feature. Which one is this? I've argued in the past that this is a basic feature missing from 4GL languages, and a lot of work in every project is wasted on hand-rolling in-memory databases left and right, without realizing it. It would seem I've missed a language that recognized this fact? (But then, so did most of the industry.)