mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove trailing whitespace

Browse Source
This commit is contained in:
Stephane Raux 2019-12-10 00:00:25 -08:00 committed by stephaneyfx
parent fe6ddd5d15
commit 1a26df7727
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/liballoc/boxed.rs
View File

@ -73,14 +73,14 @@
//! //!
//! ```c //! ```c
//! /* C header */ //! /* C header */
//! //!
//! /* Returns ownership to the caller */ //! /* Returns ownership to the caller */
//! struct Foo* foo_new(void); //! struct Foo* foo_new(void);
//! //!
//! /* Takes ownership from the caller; no-op when invoked with NULL */ //! /* Takes ownership from the caller; no-op when invoked with NULL */
//! void foo_delete(struct Foo*); //! void foo_delete(struct Foo*);
//! ``` //! ```
//! //!
//! These two functions might be implemented in Rust as follows. Here, the //! These two functions might be implemented in Rust as follows. Here, the
//! `struct Foo*` type from C is translated to `Box<Foo>`, which captures //! `struct Foo*` type from C is translated to `Box<Foo>`, which captures
//! the ownership constraints. Note also that the nullable argument to //! the ownership constraints. Note also that the nullable argument to
@ -99,7 +99,7 @@
//! #[no_mangle] //! #[no_mangle]
//! pub extern "C" fn foo_delete(_: Option<Box<Foo>>) {} //! pub extern "C" fn foo_delete(_: Option<Box<Foo>>) {}
//! ``` //! ```
//! //!
//! Even though `Box<T>` has the same representation and C ABI as a C pointer, //! Even though `Box<T>` has the same representation and C ABI as a C pointer,
//! this does not mean that you can convert an arbitrary `T*` into a `Box<T>` //! this does not mean that you can convert an arbitrary `T*` into a `Box<T>`
//! and expect things to work. `Box<T>` values will always be fully aligned, //! and expect things to work. `Box<T>` values will always be fully aligned,