A subset of this kind of tricks are usually embedded in the source code of any project of decent size or larger. But that sort of implementation usually comes w

A subset of this kind of tricks are usually embedded in the source code of any project of decent size or larger. But that sort of implementation usually comes with big disclaimers that spell out the hacky parts in very loud terms. I'm kind of wary of a library trying to glue new behaviour onto C on a general level. There are inevitably too many corner-cases which break the newly built abstraction. Those corner-cases can be explained away for one specific codebase that already comes with its own set of practices, rules of thumb, and coding patterns that the programmers are already forced to learn. But a library as general as this is easily used liberally, even casually, and without a complete map of the shortcomings and broken corners I can see lots of potential hair-pulling coming right up when things are no longer what they seem they should be.