Skip to content

Make it possible to time out after a deadline #1

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
May 15, 2024

Conversation

sbarral
Copy link
Member

@sbarral sbarral commented May 15, 2024

No description provided.

@sbarral sbarral force-pushed the main branch 2 times, most recently from 867f51a to 972dfd0 Compare May 15, 2024 11:58
@sbarral sbarral force-pushed the feature/wait-until-or-timeout branch from 75d214e to 7cde07e Compare May 15, 2024 12:08
@sbarral sbarral merged commit 84ea682 into main May 15, 2024
7 checks passed
@Urgau
Copy link

Urgau commented May 24, 2024

Heads up, with the release of rust-lang/cargo#13913 (in nightly-2024-05-19), Cargo has now gain the ability to declare --check-cfg args directly inside the [lints] table with [lints.rust.unexpected_cfgs.check-cfg]1:

Cargo.toml:

[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg = ['cfg(foo)'] }

Note that the diagnostic output of the lint has been updated to suggest the [lints] approach first. You can use it to guide you through the --check-cfg arguments that may need to be added.

Footnotes

  1. take effect on Rust 1.80 (current nightly), is ignored on Rust 1.79 (current beta), and produce an unused warning below

@sbarral
Copy link
Member Author

sbarral commented May 24, 2024

Heads up, with the release of rust-lang/cargo#13913 (in nightly-2024-05-19), Cargo has now gain the ability to declare --check-cfg args directly inside the [lints] table with [lints.rust.unexpected_cfgs.check-cfg]1:

HUGE thanks!

@sbarral sbarral deleted the feature/wait-until-or-timeout branch September 8, 2024 20:23
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants