Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Custom type names aren't treated as real type names. #2073

Closed
mhammond opened this issue Apr 15, 2024 · 1 comment
Closed

Custom type names aren't treated as real type names. #2073

mhammond opened this issue Apr 15, 2024 · 1 comment

Comments

@mhammond
Copy link
Member

This means they may end up using names which generate warnings from bindings, or fail completely if the name is a keyword. The names of custom types should be consistent with all other type names.
@mhammond
Copy link
Member Author

mhammond commented May 3, 2024

oops, fixed in #2074

@mhammond mhammond closed this as completed May 3, 2024
@thunderbiscuit thunderbiscuit mentioned this issue Jun 24, 2024
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mhammond