A new tool for fighting against Hyrum’s law in ... concept-driven design
summary
Argues that Hyrum’s law is controllable by shipping models that intentionally break implicit behavior, demonstrates this with a container iterator invalidation test and with Kokkos execution/memory-space examples, and builds a Kokkos logical memory space plus poisoning via sanitizer library that fakes inaccessibility. The demo runs as a profiling plugin, triggers an assertion failure exactly at the offending line, and proves the tooling catches accidental reliance on synchronous or host-accessible memory before GPU deployment.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:13Outline and goals
- 0:55Hiram's Law and implicit APIs
- 3:00The library-client relation
- 5:30Concept driven design
- 8:09Contrived example: Containers
- 11:05Breaking models for testing
- 13:11Kokkos background
- 15:54Parallelism example
- 20:24Breaking real-world models
- 22:54Live demo: Memory poisoning
- 26:17Conclusion and Q&A
related talks
17mCode-Specify-Test-Debug-Prove: Flexibly Integrating Separation Logic Specification into(…)
01h 04mWe Live in Interesting Times
50mSmashing the Stack: Let’s Make It Less Fun And Unprofitable!
26mAn Effective Approach to Software Obfuscation
27mLet's Bring System Dynamics Back to CS!
51mStretching the Glasgow Haskell Compiler: Nourishing GHC with Domain-Driven De...
29müberSpark: Enforcing Verifiable Object Abstractions for Automated...
21mAbstract Debuggers: Exploring Program Behaviors Using Static Analysis Results