So basically a signature that is a combination of all the types. I'm thinking the name of the parameters should be numbered like what is shown above to not create too much complexity. I could probably add a unionize method to TypeDefinition that handles creating the union types.
For example:
Should have two overload signatures and one implementation signature. Right now it uses the last signature for the implementation signature.
The implementation signature should be (this is kind of a compromise to make this scenario work within the library):
So basically a signature that is a combination of all the types. I'm thinking the name of the parameters should be numbered like what is shown above to not create too much complexity. I could probably add a
unionize
method toTypeDefinition
that handles creating the union types.