Types Don't Know #
summary
Proposes a concrete hashing infrastructure that decouples algorithms from types into three roles (type authors provide hash_append, algorithm authors provide an init/update/finalize adapter, clients supply a std::uhash), ships a reference implementation on GitHub and a committee paper, and yields composable, easily swapped hash functors with optional seeding and an is_contiguously_hashable trait. One practical exception is cityhash which needs whole-buffer input; Bloomberg already implements this, so the idea is demonstrably usable.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:47Overview
- 3:07Issues
- 8:12Anatomy Of A Hash Function
- 28:24To use hash_append
- 31:29To Change Hashing Algorithms
- 35:14Set Up Defaults
- 35:57Details
- 44:55Benefits
- 46:08Types Don't Know #
related talks
46mType safe C++? LOL!
01h 02mDiscovering a User-Facing Concept
54mA Tour of C++ Recognised User Type Categories
01h 01mConcepts vs Typeclasses vs Traits vs Protocols
01h 03mTemplate Metaprogramming: Practical Application
49mThe Trouble With Types
36mCommunicating in Types
01h 02mDiscovering a User-Facing Concept