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
Switch defaults from generating unstable Rust to generating stable Rust #757
Comments
Hi! If you have any questions regarding this issue, feel free to make a comment here, or ask it in the If you intend to work on this issue, then add |
I'll take a stab at this one. @highfive: assign me |
Hey @jonstites! Thanks for your interest in working on this issue. It's now assigned to you! |
- changing the Builder::no_unstable_rust method to the Builder::unstable_rust method - changing the --no-unstable-rust flag to a --unstable-rust flag in src/options.rs - changing bindgen-option header in the test headers to remove the --no-unstable-rust flag Fixes rust-lang#757
@jonstites sorry, didn't see you had taken it :/ |
- changing the Builder::no_unstable_rust method to the Builder::unstable_rust method - changing the --no-unstable-rust flag to a --unstable-rust flag in src/options.rs - changing bindgen-flags header in the test headers to remove the --no-unstable-rust flag Fixes rust-lang#757
- changing the Builder::no_unstable_rust method to the Builder::unstable_rust method - changing the --no-unstable-rust flag to a --unstable-rust flag in src/options.rs - changing bindgen-flags header in the test headers to remove the --no-unstable-rust flag Fixes rust-lang#757
switch defaults from generating unstable Rust to generating stable Rust As said in the issue: - changing the Builder::no_unstable_rust method to the Builder::unstable_rust method - changing the --no-unstable-rust flag to a --unstable-rust flag in src/options.rs - changing bindgen-flags header in the test headers to remove the --no-unstable-rust flag - removing --no-unstable-rust flag in ./test/test-one.sh Fixes #757 r? @fitzgen
The current default is definitely the wrong choice.
This involves
changing the
Builder::no_unstable_rust
method to theBuilder::unstable_rust
methodchanging the
--no-unstable-rust
flag to a--unstable-rust
flag insrc/options.rs
I don't think this will require updating test results since we run all the tests with
--no-unstable-rust
, however it may require removing that flag from the test harness. I suggetgit grep
ing for "unstable" to see places in the code base that may require updating.The text was updated successfully, but these errors were encountered: