From b2db08a014478874b581fca06a8c62eee05e1d28 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon, 1 Jan 2024 16:23:42 +0000 Subject: [PATCH] build(deps): bump serde_yaml from 0.9.28 to 0.9.29 (#1630) Bumps [serde_yaml](https://github.com/dtolnay/serde-yaml) from 0.9.28 to 0.9.29.
Release notes

Sourced from serde_yaml's releases.

0.9.29

Commits

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=serde_yaml&package-manager=cargo&previous-version=0.9.28&new-version=0.9.29)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) ---
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- Cargo.lock | 4 ++-- src/slices-and-lifetimes/lifetime-elision.md | 8 ++++---- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/Cargo.lock b/Cargo.lock index 0316036f..19de411a 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -2076,9 +2076,9 @@ dependencies = [ [[package]] name = "serde_yaml" -version = "0.9.28" +version = "0.9.29" source = "registry+https://github.com/rust-lang/crates.io-index" -checksum = "9269cfafc7e0257ee4a42f3f68a307f458c63d9e7c8ba4b58c5d15f1b7d7e8d3" +checksum = "a15e0ef66bf939a7c890a0bf6d5a733c70202225f9888a89ed5c62298b019129" dependencies = [ "indexmap", "itoa", diff --git a/src/slices-and-lifetimes/lifetime-elision.md b/src/slices-and-lifetimes/lifetime-elision.md index 1eec1005..9a55ee3e 100644 --- a/src/slices-and-lifetimes/lifetime-elision.md +++ b/src/slices-and-lifetimes/lifetime-elision.md @@ -69,9 +69,9 @@ by the compiler. Note that this is not the case for raw pointers (unsafe), and this is a common source of errors with unsafe Rust. Students may ask when to use lifetimes. Rust borrows _always_ have lifetimes. -Most of the time, elision and type inference mean these don't need to be -written out. In more complicated cases, lifetime annotations can help resolve -ambiguity. Often, especially when prototyping, it's easier to just work with -owned data by cloning values where necessary. +Most of the time, elision and type inference mean these don't need to be written +out. In more complicated cases, lifetime annotations can help resolve ambiguity. +Often, especially when prototyping, it's easier to just work with owned data by +cloning values where necessary.