Skip to content

Conversation

@jjonescz
Copy link
Member

No description provided.

@CyrusNajmabadi
Copy link
Member

Dumb quesstion. Why is this not a normal binding time error? why does it happen during build only?

@jjonescz
Copy link
Member Author

Currently this error is reported inside TypeNameSerializer whenever it visits a function pointer. That seems more reliable than trying to figure out all the places in binding which could lead to us trying to serialize a fnptr later during emit. But it could definitely be improved by catching at least some places during binding and leaving the emit error as a fallback.

@CyrusNajmabadi
Copy link
Member

That seems more reliable than trying to figure out all the places in binding which could lead to us trying to serialize a fnptr later during emit.

Thanks :) If it is too complex to check during binding, that makes sense to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants