about summary refs log tree commit diff
diff options
context:
space:
mode:
authorkennytm <kennytm@gmail.com>2018-01-13 02:26:38 +0800
committerkennytm <kennytm@gmail.com>2018-01-13 03:16:55 +0800
commitcf70a48ce4691b4d3a3b81acc7452e2da15d1979 (patch)
tree4582e29c8643aa17ba9dc4b57637d70fc6f54b99
parent30dbbb528dc315506d1ac28122953356c6d1e2fb (diff)
parent9d9504a27c240f3e04bec95e382f8130282cca36 (diff)
downloadrust-cf70a48ce4691b4d3a3b81acc7452e2da15d1979.tar.gz
rust-cf70a48ce4691b4d3a3b81acc7452e2da15d1979.zip
Rollup merge of #47340 - alercah:typo-fix, r=GuillaumeGomez
Fix typo.
-rw-r--r--src/libstd/ffi/mod.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libstd/ffi/mod.rs b/src/libstd/ffi/mod.rs
index a75596351e4..a37a5e8ae82 100644
--- a/src/libstd/ffi/mod.rs
+++ b/src/libstd/ffi/mod.rs
@@ -53,7 +53,7 @@
 //! 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 (becasue the
+//! 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
 //! length needs to be computed by scanning the string for the nul
 //! terminator.