Don't match macros on exact type names

[andybarron]

See this comment on a previous issue. Matching macros on exact type names prevents users from calling the macros with fully qualified type names or typedefs.

Possible solutions include trait specialization (which will likely be unstable for some time) and std::any trickery.

[dragostis]

@andybarron I'm planning on solving #90 and the rest of the small bugs soon. The way I see it, with these solved, this would be a pretty good time to release 1.0.0, apart from this current issue. Should I postpone the release until this one is solved as well?

[dragostis]

I gave this a shot, but I don't really see how this could be done without procedural macros. One reason why this doesn't work is that if you keep the argument types opaque in tys, you won't know anything about the mutability of the object that must be bound to the current argument's name. Another one would be the return type.

With procedural macros and trait specialization, this would be easy: see mutability in order to bind to the specified argument name and use trait specialization in order to allocate and convert the objects.