move #![allow(unexpected_cfgs)] to crate root#233
Merged
Conversation
micahrj
force-pushed
the
unexpected-cfgs
branch
from
46e02fb to
ec63e5b
Compare
geom3trik
approved these changes
Apr 25, 2026
micahrj
force-pushed
the
unexpected-cfgs
branch
from
ec63e5b to
7e3864f
Compare
micahrj
changed the title
objc crate
This was referenced Apr 25, 2026
wrl
approved these changes
Apr 28, 2026
This was referenced Apr 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CI builds are failing due to warnings caused by macros from the
objccrate (msg_send!,sel!, andclass!). The existing module-level#![allow(unexpected_cfgs)]attributes apparently no longer work to silence these warnings, but moving the attribute to the crate root seems to work.Fixes #229.
Also run
cargo fmtso that formatting check passes.