Skip to content
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

re-enable "unexpected_cfgs" lint #42

Merged
merged 1 commit into from
May 25, 2024

Conversation

simonwuelker
Copy link
Contributor

Closes #34

Enables the unexpected_cfgs lint as described in #34 (comment)

src/lib.rs Show resolved Hide resolved
Previously, this lint was disabled because
it would not accept custom cfg values unless
a build.rs was added (which is undesirable).

Now, reachable cfgs can be configured from
Cargo.toml, so this is what we should do.
@simonwuelker simonwuelker force-pushed the reenable-unexpected-cfgs-lint branch from b5ab39b to d4e22af Compare May 25, 2024 07:30
@faern
Copy link
Owner

faern commented May 25, 2024

Nice. Thank you!

@faern faern merged commit f2846be into faern:main May 25, 2024
11 checks passed
@faern
Copy link
Owner

faern commented May 25, 2024

I realize we need to make loom a conditional dependency in some way. As it stands currently cargo treats it as a mandatory dependency and the dependency graph becomes quite large, which is terrible for many reasons. This is supposed to be a lightweight crate.

I just found https://crates.io/crates/oneshot-uniffi, and that made it even more apparent.

@faern
Copy link
Owner

faern commented May 25, 2024

I will explore that: #43

@simonwuelker simonwuelker deleted the reenable-unexpected-cfgs-lint branch May 25, 2024 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Custom cfg loom makes cargo spam warnings
2 participants