Skip to content

Conversation

maurer
Copy link

@maurer maurer commented Sep 4, 2025

Fixes #3287

This addresses the issue by checking if the type the constant is being generated for has a newtype alias applied to it.

@maurer maurer force-pushed the wrap-newtype-consts branch 2 times, most recently from 25e3a0b to abe5208 Compare September 4, 2025 23:59
@maurer
Copy link
Author

maurer commented Sep 5, 2025

String new-type-alias constants are not currently supported by this PR because new-type-alias currently converts the typedef into Foo(*const c_char) which isn't going to be compatible with the constant representation.

@maurer maurer force-pushed the wrap-newtype-consts branch 4 times, most recently from cf52008 to 1c2d65f Compare September 5, 2025 17:29
@maurer maurer force-pushed the wrap-newtype-consts branch from 1c2d65f to f369096 Compare September 5, 2025 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

new_type_alias breaks constant generation
1 participant