about summary refs log tree commit diff
diff options
context:
space:
mode:
authorGodfrey Chan <godfreykfc@gmail.com>2024-09-03 11:43:03 -0700
committerGitHub <noreply@github.com>2024-09-03 11:43:03 -0700
commit3626b66af05e00b7b836a620e0d5236a64f3a89b (patch)
tree1cae40d6066c72d88c9f3ad7da8d026866388b24
parent65e78db8d7b41ec40fd9b789a96df12fd3d18180 (diff)
downloadrust-3626b66af05e00b7b836a620e0d5236a64f3a89b.tar.gz
rust-3626b66af05e00b7b836a620e0d5236a64f3a89b.zip
Update marker.rs
-rw-r--r--library/core/src/marker.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/library/core/src/marker.rs b/library/core/src/marker.rs
index 91ec046eeab..dfc988c885e 100644
--- a/library/core/src/marker.rs
+++ b/library/core/src/marker.rs
@@ -299,7 +299,7 @@ marker_impls! {
 ///
 /// This isn't always desired. For example, shared references (`&T`) can be copied regardless of
 /// whether `T` is `Copy`. Likewise, a generic struct containing markers such as [`PhantomData`]
-/// could potentially be duplicated with a bit-wise copy. 
+/// could potentially be duplicated with a bit-wise copy.
 ///
 /// ## What's the difference between `Copy` and `Clone`?
 ///