-
Notifications
You must be signed in to change notification settings - Fork 126
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
Allow generation of exported and non exported types from the same generic code. #66
Comments
jsouthworth
added a commit
to jsouthworth/genny
that referenced
this issue
Oct 17, 2020
This allows one to create an exported template type and create a non exported type from that template. Fixes cheekybits#66 of internal types for the generic types.
jsouthworth
added a commit
to jsouthworth/genny
that referenced
this issue
Oct 17, 2020
This allows one to create an exported template type and create a non exported type from that template. Fixes cheekybits#66
jsouthworth
added a commit
to jsouthworth/genny
that referenced
this issue
Oct 19, 2020
This allows one to create an exported template type and create a non exported type from that template. Fixes cheekybits#66
jsouthworth
added a commit
to jsouthworth/genny
that referenced
this issue
Oct 19, 2020
This allows one to create an exported template type and create a non exported type from that template. Fixes cheekybits#66
jsouthworth
added a commit
to jsouthworth/genny
that referenced
this issue
Oct 19, 2020
This allows one to create an exported template type and create a non exported type from that template. Fixes cheekybits#66
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice to not pollute a package's namespace with exported types that are not useable from outside of the package due to the use of internal types for the generic types. One way to do this is to add a 'private' flag to the parse.Generics function and to switch from specificLg to specificSm in subIntoLiteral if this flag is set.
The text was updated successfully, but these errors were encountered: