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

tutorial: Delete 'what to be aware of'

Browse Source 
This section associates borrowed pointers purely with stack allocation, which
is confusing. The following sections explain pointers in detail.
This commit is contained in:
Brian Anderson 2012-09-26 18:36:36 -07:00
parent 8f0e9ff029
commit 3232e75995
1 changed files with 0 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/tutorial.md
View File

@ -995,15 +995,6 @@ _owned boxes_. All tasks may allocate objects on the exchange heap,
then transfer ownership of those objects to other tasks, avoiding
expensive copies.
## What to be aware of
Rust has three "realms" in which objects can be allocated: the stack,
the local heap, and the exchange heap. These realms have corresponding
pointer types: the borrowed pointer (`&T`), the managed box (`@T`),
and the owned box (`~T`). These three sigils will appear
repeatedly as we explore the language. Learning the appropriate role
of each is key to using Rust effectively.
# Boxes and pointers
In contrast to a lot of modern languages, aggregate types like structs