-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using generic schema as type for another generic schema #703
Comments
This is probably something that needs a little or perhaps even more investigation and exploration. I don't have the time to get to this right now, but perhaps this could be addressed in future. The generics are quite troublesome because of the design of the A word of caution. It might be possible to support this behavior but same goes other way as well. This functionality might be difficult or near impossible to implement. |
There is now new implementation for generics coming up in #1034 which should solve the issue with aliases approach. |
@juhaku Thank you very much for solving the problems with generics and of course for your time for doing this. |
Thank you for giving inspiration for the solution. It is somewhat based on your example. |
Description
Hi, as mentioned in the title, I want to use a generic schema as a type for another generic schema.
The problem
All aliases for GenericStructA<T> prompt error messages.
What do I expect?
GenericStructAString, GenericStructAInt, and GenericStructANotGenericStruct will create references to GenericStructBString, GenericStructBInt, and GenericStructBNotGenericStruct. Or even better I don't have to create those aliases for GenericStructB<T> and they will be created automatically by creating those aliases for GenericStructA<T>
The text was updated successfully, but these errors were encountered: