Skip to content

Conversation

@inkreasing
Copy link
Owner

No description provided.

@inkreasing
Copy link
Owner Author

@cjappl don't know if you want to look at everything.

First commit should be no functional change and just enabled me to later add more detailed sanitizer information.

Second commit actually adds rtsan in the parser, the existing checks for the sanitizer setting and the codegen backend.

Third commit is "optional". It adds a warning if someone uses rtsan with async functions, which doesn't really work. I don't know if the rust project actually wants this, so i keep the seperate commit.

Copy link

@cjappl cjappl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, looks reasonable to me, about what I would expect (without digging into the dirty details)

Thanks

@inkreasing inkreasing force-pushed the rtsan-with-async-warning branch from f461fe9 to f0e2360 Compare October 20, 2025 21:26
@inkreasing inkreasing force-pushed the rtsan-with-async-warning branch from f0e2360 to 0760962 Compare October 23, 2025 15:26
@inkreasing inkreasing closed this Nov 8, 2025
@inkreasing inkreasing deleted the rtsan-with-async-warning branch November 9, 2025 08:52
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.

3 participants