You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't straightforward because something about 944ee530cd04712021ee21a60f1ef59d2ab6d489 broke our libc_bitflags! macro with the following error:
Compiling bitflags v0.9.1Compiling nix v0.10.0-pre
error: no rules expected the token `cfg(any(target_os = "android", target_os = "linux"))`
--> src/macros.rs:129:19
|
129 | #[$attr]
| ^^^^^
|
::: src/fcntl.rs
|
11 | / libc_bitflags!{12 | | pubstructAtFlags: c_int {13 | | AT_SYMLINK_NOFOLLOW;14 | | #[cfg(any(target_os = "android", target_os = "linux"))]
... |
18 | | }19 | | }
| |_- in this macro invocation
error:Could not compile `nix`.To learn more, run the command again with --verbose.
So that should get figured out so we get nice constant scoping in our docs. Note that this will require use to require 1.20 as our minimum Rust version, but I think it's worth it for us to switch to that because of the significant documentation win.
The text was updated successfully, but these errors were encountered:
801: Upgrade to Bitflags 1.0 r=asomers a=Susurrus
The libc_bitflags! macro was replaced with a non-recursive one supporting
only public structs. I could not figure out how to make the old macro work
with the upgrade, so I reworked part of the bitflags! macro directly to suit
our needs, much as the original recursive macro was made. There are no uses
of this macro for non-public structs, so this is not a problem for internal code.
Closes#766.
This isn't straightforward because something about 944ee530cd04712021ee21a60f1ef59d2ab6d489 broke our
libc_bitflags!
macro with the following error:So that should get figured out so we get nice constant scoping in our docs. Note that this will require use to require 1.20 as our minimum Rust version, but I think it's worth it for us to switch to that because of the significant documentation win.
The text was updated successfully, but these errors were encountered: