-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add CI to ensure definitions are not removed #270
Comments
Yeah I'd love to have a check like this! On Wednesday, April 27, 2016, Kamal Marhubi notifications@github.com
|
select(2) fixes Part of rust-lang#270, fixed according to @kamalmarhubi's comments.
New syscalls Part of rust-lang#270
I'm going to try to use the |
Verify that only non-technical breaking changes are applied to libc Closes #270 . cc @alexcrichton so this would be a solution to #270 that uses rust-semverver to check that the API of `libc` contains only non-technical breaking changes. This is a WIP and uses a fork of `rust-semverver` for now, but I've sent PRs upstream already. This is the only idea I have for solving #270 . `rust-semverver` is not perfect, but it can deal with functions, consts, and simple structs just fine, and that's pretty much everything that libc uses. cc @ibabushkin Some other notes: * we have to compile `rust-semverver` for each toolchain version, and it depends on `cargo` so we have to build ~160 dependencies. Using `cache: cargo` breaks everything.
In #269 I moved some definitions around in the hierarchy, and ended up losing some functions for a while. Ideally we'd have something in CI that compares API coverage against
TRAVIS_BRANCH
/APPVEYOR_REPO_BRANCH
to ensure we're only ever adding APIs.The text was updated successfully, but these errors were encountered: