These are chat archives for boostorg/hana
But doesn’t that create problems because some types are not allowed from appearing as function arguments?
Yes, I didn't think of that. I suppose the user could use
hana::type or something similar to wrap only those corner cases, but that would still be annoying. Still, I wonder how it would perform against existing type list implementations. Also, it would be an interesting syntax... something like
using f = param_list(char, short, long);
I'm going to add some lightweight tuple-y stuff to CallableTraits, since those operations are the only ones missing to solve the function-type-specialization-spam problem that the project attempts to solve - i.e. there's currently no way to
push_args_front on a signature without having to go through the template specialization rigmarole, so I'll throw it in the functionality for now (and maybe take it out later). Since my use case concerns real parameter types, the restrictions you mentioned aren't a problem for me (but would be for a generic type container).
Just wanted to see if you'd been down that road. Thanks!