Yeah, that’s the strongest argument against something like this. My answer you quoted also included the suggestion of some explicit way to provide generic bounds. Similarly, one could also require an explicit annotation for a field-based implementation (and that could even be limited to the cases without leakage or potential for breakage that I explained above). Some code examples are in this comment from an earlier thread