On Fri Jun 7 14:39:29 2024 +0000, Gabriel Ivăncescu wrote:
I see, if you look at it that way it makes sense to use IID, yeah (I was thinking of the functions as complete separate entities rather than interface implementations). I still think it's slightly better to just pass/store func_info_t as a container though—it's not just the args but everywhere else we need to store it (like in ProxyFunction as I mentioned), now it's one less field to worry about. And besides, if we ever do need to change it at some point later, it will be much easier without affecting call sites.
Current func info is more than (id,iid) carrier, it would only make things more confusing to reuse it as an opaque with constrains like that. We could introduce a new struct, if needed.