Skip to content

Conversation

@mkeeter
Copy link
Contributor

@mkeeter mkeeter commented Aug 15, 2025

Rust 1.89 includes a new lint for mismatched lifetime syntaxes. This PR fixes those warnings!

@mkeeter
Copy link
Contributor Author

mkeeter commented Aug 18, 2025

The Lints CI check failed due to an unnecessary return; this is now fixed as well.

@RaoulLuque RaoulLuque added A-crate Area: Petgraph crate functionality C-refactor Category: PR/issue with specific code/suggestions for refactoring labels Aug 25, 2025
@mkeeter
Copy link
Contributor Author

mkeeter commented Aug 26, 2025

There are lots of PR failing CI due to these lints – can this be merged now?

(I see that you approved the PR, but I don't have permission to merge it)

@RaoulLuque
Copy link
Member

Good point, yeah of course 👍

@RaoulLuque RaoulLuque added this pull request to the merge queue Aug 26, 2025
Merged via the queue into petgraph:master with commit 4d807c1 Aug 26, 2025
11 checks passed
@mkeeter mkeeter deleted the add-lifetimes branch August 26, 2025 15:42
RaoulLuque pushed a commit to RaoulLuque/petgraph that referenced this pull request Sep 21, 2025
<!--
  -- Thanks for contributing to `petgraph`!
  --
-- We require PR titles to follow the Conventional Commits
specification,
-- https://www.conventionalcommits.org/en/v1.0.0/. This helps us
generate
  -- changelogs and follow semantic versioning.
  --
  -- Start the PR title with one of the following:
  --  * `feat:` for new features
  --  * `fix:` for bug fixes
  --  * `refactor:` for code refactors
  --  * `docs:` for documentation changes
  --  * `test:` for test changes
  --  * `perf:` for performance improvements
  --  * `revert:` for reverting changes
  --  * `ci:` for CI/CD changes
-- * `chore:` for changes that don't fit in any of the above categories
  -- The last two categories will not be included in the changelog.
  --
-- If your PR includes a breaking change, please add a `!` after the
type
-- and include a `BREAKING CHANGE:` line in the body of the PR
describing
  -- the necessary changes for users to update their code.
  --
  -->
Rust 1.89 includes [a new
lint](https://blog.rust-lang.org/2025/08/07/Rust-1.89.0/#mismatched-lifetime-syntaxes-lint)
for mismatched lifetime syntaxes. This PR fixes those warnings!
RaoulLuque pushed a commit to cactusdualcore/petgraph that referenced this pull request Sep 21, 2025
<!--
  -- Thanks for contributing to `petgraph`! 
  --
-- We require PR titles to follow the Conventional Commits
specification,
-- https://www.conventionalcommits.org/en/v1.0.0/. This helps us
generate
  -- changelogs and follow semantic versioning.
  --
  -- Start the PR title with one of the following:
  --  * `feat:` for new features
  --  * `fix:` for bug fixes
  --  * `refactor:` for code refactors
  --  * `docs:` for documentation changes
  --  * `test:` for test changes
  --  * `perf:` for performance improvements
  --  * `revert:` for reverting changes
  --  * `ci:` for CI/CD changes
-- * `chore:` for changes that don't fit in any of the above categories
  -- The last two categories will not be included in the changelog.
  --
-- If your PR includes a breaking change, please add a `!` after the
type
-- and include a `BREAKING CHANGE:` line in the body of the PR
describing
  -- the necessary changes for users to update their code.
  --
  -->
Rust 1.89 includes [a new
lint](https://blog.rust-lang.org/2025/08/07/Rust-1.89.0/#mismatched-lifetime-syntaxes-lint)
for mismatched lifetime syntaxes. This PR fixes those warnings!
RaoulLuque pushed a commit to RaoulLuque/petgraph that referenced this pull request Sep 21, 2025
<!--
  -- Thanks for contributing to `petgraph`! 
  --
-- We require PR titles to follow the Conventional Commits
specification,
-- https://www.conventionalcommits.org/en/v1.0.0/. This helps us
generate
  -- changelogs and follow semantic versioning.
  --
  -- Start the PR title with one of the following:
  --  * `feat:` for new features
  --  * `fix:` for bug fixes
  --  * `refactor:` for code refactors
  --  * `docs:` for documentation changes
  --  * `test:` for test changes
  --  * `perf:` for performance improvements
  --  * `revert:` for reverting changes
  --  * `ci:` for CI/CD changes
-- * `chore:` for changes that don't fit in any of the above categories
  -- The last two categories will not be included in the changelog.
  --
-- If your PR includes a breaking change, please add a `!` after the
type
-- and include a `BREAKING CHANGE:` line in the body of the PR
describing
  -- the necessary changes for users to update their code.
  --
  -->
Rust 1.89 includes [a new
lint](https://blog.rust-lang.org/2025/08/07/Rust-1.89.0/#mismatched-lifetime-syntaxes-lint)
for mismatched lifetime syntaxes. This PR fixes those warnings!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-crate Area: Petgraph crate functionality C-refactor Category: PR/issue with specific code/suggestions for refactoring

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants