about summary refs log tree commit diff
path: root/library/std/src/ffi
diff options
context:
space:
mode:
authorr00ster91 <r00ster91@protonmail.com>2021-09-24 12:44:28 +0200
committerr00ster91 <r00ster91@protonmail.com>2021-09-24 12:44:28 +0200
commit956f87fb04f589ac2fbe262a043c9f3cad6b2ac0 (patch)
tree12e105b117702a39fbe0e11c2b8702025c5ecc66 /library/std/src/ffi
parent197fc8591e6b02ac1f359ee0a72616eb4a6d4f4c (diff)
downloadrust-956f87fb04f589ac2fbe262a043c9f3cad6b2ac0.tar.gz
rust-956f87fb04f589ac2fbe262a043c9f3cad6b2ac0.zip
consistent big O notation
Diffstat (limited to 'library/std/src/ffi')
-rw-r--r--library/std/src/ffi/mod.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/library/std/src/ffi/mod.rs b/library/std/src/ffi/mod.rs
index fe4e3af91ad..84d65bb3df4 100644
--- a/library/std/src/ffi/mod.rs
+++ b/library/std/src/ffi/mod.rs
@@ -43,8 +43,8 @@
 //! terminator, so the buffer length is really `len+1` characters.
 //! Rust strings don't have a nul terminator; their length is always
 //! stored and does not need to be calculated. While in Rust
-//! accessing a string's length is a `O(1)` operation (because the
-//! length is stored); in C it is an `O(length)` operation because the
+//! accessing a string's length is an *O*(1) operation (because the
+//! length is stored); in C it is an *O*(*n*) operation because the
 //! length needs to be computed by scanning the string for the nul
 //! terminator.
 //!