News for hackers. Stuff that matters.
Re:C++: Associative map containers with compile-time lookup by hogliux on Tuesday October 23, 2018 @04:50PM (#18287359)
Hmmm, I'm not sure I understand. You can't really mark `static static_map<>::Value& get()` constexpr because it returns a value which is only known at run-time - again the value is a run-time value, only the lookup (where in memory) is at compile-time. This has nothing to do with inlining.
Re:C++: Associative map containers with compile-time lookup by gumby on Tuesday October 23, 2018 @05:58PM (#18287889)
Ahh, I looked in the source and see that runtime_map is simply a std::unordered_map.

I didn't look closely enough and assumed you'd made your own hash lookup so that parts of it could be run at compile time (in fact you could intern compile-time keys statically in the front of an object (in the initialized data section of the object file) adding a single additional probe at runtime) and let the linker patch up the locations in the usual fashion.

This is all a move in the right direction!