Skip to content

Conversation

@camc314
Copy link

@camc314 camc314 commented Nov 19, 2025

your choice boshen if we merge this, it was kind of as an outcome of the few panics we recieved because symbol/ref IDs weren't set, so this felt like a good thing to check in CI. But since this code doesn't change much it might not be worth adding a job for it

Copy link
Author

camc314 commented Nov 19, 2025

This stack of pull requests is managed by Graphite. Learn more about stacking.

@camc314 camc314 force-pushed the c/11-19-feat_add_semanticidsrunner_for_symbol_reference_id_validation branch from 8b56def to 903951e Compare November 19, 2025 11:07
@camc314 camc314 marked this pull request as ready for review November 20, 2025 09:04
@Dunqing
Copy link
Member

Dunqing commented Nov 22, 2025

Yes, it isn't worth doing in a separate job. However, we can move this check to a job that requires building semantics, e.g., a transformer; you can run the check after semantic data has been built. I think it does the same thing as you want.

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.

4 participants