Skip to content

Conversation

@alexcrichton
Copy link
Member

@alexcrichton alexcrichton commented Dec 10, 2025

These were added way back when in #2499 and while they may have existed in a historical version of wasi-libc they most certainly do not exist in the current wasi-libc. Any usage of them is already-breaking, so this deletes these items.

These were added way back when in rust-lang#2499 and while they may have existed
in a historical version of wasi-libc they most certainly do not exist in
the current wasi-libc. Any usage of them is already-breaking, so this
deletes these items.
@alexcrichton
Copy link
Member Author

This is something I'd ideally like to backport to the 0.2 version as well, although naturally it's a strictly-speaking breaking change. Technically historical changes like ca20d7d were also breaking in a minor fashion too, but this in theory could have higher impact because it's a more C-like constant rather than something libc-specific.

Basically I don't know what the fallout of this would be. Extrapolating the highest risk is a crate that uses these constants in platform-specific code, including WASI, but the code is dead at runtime so no one noticed that it wouldn't work if it were executed. I'm not sure how prevalent such a situation is, however.

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