nostr:npub1qnnjpjm3gctvgewlz0pc8hk8tzu0gewskh4fewgmuvjm9kw2l4usagw7ad interesting idea, but I don't often see intentional field updates being instrumented, the way allocators are. E.g. my malloc leak tracer uses a magic number to identify live allocs, and erases the number on frees. Besides alloc and free, there's no other interaction with the library. A fixed magic number would be the only thing usable for boundary checking. https://github.com/hyc/mleak