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

ci: Run clippy -Dwarnings and use minimal toolchain profile #223

Merged
merged 4 commits into from
Feb 1, 2022

Conversation

MarijnS95
Copy link
Collaborator

No description provided.

@MarijnS95
Copy link
Collaborator Author

@msiglreith Can we get this in?

Copy link
Contributor

@msiglreith msiglreith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure (:

@msiglreith msiglreith merged commit 72a538d into gfx-rs:master Feb 1, 2022
@MarijnS95 MarijnS95 deleted the ci-clippy branch February 1, 2022 22:49
@@ -6,6 +6,7 @@ authors = [
"Lei Zhang <antiagainst@gmail.com>",
]
edition = "2018"
rust-version = "1.58"
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3 years later, I don't understand why I added this: autogen is the only crate that is not published and shouldn't care about the version at all, since Rust developers contributing to this repository and specifically using the generator to regenerate its contents can easily use the latest stable at all times.

MarijnS95 added a commit that referenced this pull request Nov 1, 2024
Specifically `rust-version = "1.58"` in the `autogen` module that
I added in #223 is weird, since any developers working on and/or
contributing to the repository should easily be able to run the latest
stable and take advantage of newer Rust features in `autogen` code.
MarijnS95 added a commit that referenced this pull request Nov 1, 2024
Specifically `rust-version = "1.58"` in the `autogen` module that
I added in #223 is weird, since any developers working on and/or
contributing to the repository should easily be able to run the latest
stable and take advantage of newer Rust features in `autogen` code.
MarijnS95 added a commit that referenced this pull request Dec 27, 2024
Specifically `rust-version = "1.58"` in the `autogen` module that
I added in #223 is weird, since any developers working on and/or
contributing to the repository should easily be able to run the latest
stable and take advantage of newer Rust features in `autogen` code.
MarijnS95 added a commit that referenced this pull request Dec 28, 2024
Specifically `rust-version = "1.58"` in the `autogen` module that
I added in #223 is weird, since any developers working on and/or
contributing to the repository should easily be able to run the latest
stable and take advantage of newer Rust features in `autogen` code.
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.

2 participants