Mike Hommey
Mike Hommey
Any of the test files that were touched in e8ffb42ab66405ac56d04494a30e54b584f2d4dd shows the warning with rustc < 1.65.
There's core_io (https://crates.io/crates/core_io) but it's autogenerated at build time, which is not nice for vendoring.
IIRC, recent clang wants an API version in the target, as in `--target=armv7-linux-androideabi16`, rather than `--target=armv7-linux-androideabi`
Both would work, although the proc-macro would feel better because it groups the derive in a single place, but I can understand that it's more stuff to compile.
> The bitflags! { struct Qux: u32 { .. } } case currently just uses a newtype to make plain #[derive()]s work That's what bitflags 1 was doing. bitflags 2...
You can use macos-14 now.
> I'm not sure what to do about licensing, authorship etc. I guess you can add a GPLv2 block at the beginning of the file, add a copyright notice (year...
> Any ideas here @glandium? Nope
I'm sorting this out through my employer. (an email has been sent to member-services at unicode.org about this. My work email is different than the one in the current commit,...
The CLA should be sorted out.