Skip to content

Commit

Permalink
Fixed typos
Browse files Browse the repository at this point in the history
  • Loading branch information
mitsuhiko committed May 27, 2015
1 parent ee12c7f commit 21b3c2f
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions 2015/5/27/rust-for-pythonistas.rst
Original file line number Diff line number Diff line change
Expand Up @@ -214,7 +214,7 @@ work”. Obviously you can still generate memory leaks but most problems
will be resolved for you automatically at runtime.

In Rust however there is no garbage collector, yet the memory management
still works automatically. This is enabled by a concept know as ownership
still works automatically. This is enabled by a concept known as ownership
tracking. All things you can create are owned by another thing. If you
want to compare this to Python you could imagine that all objects in
Python are owned by the interpreter. In Rust ownership is much more
Expand Down Expand Up @@ -319,7 +319,7 @@ the Rust equivalent:
print "fib({}) = {}".format(i, rv)

So what we do here is spawn 20 threads and make them compute in a very
terrible manner increasing factorial numbers. Then we join the threads
terrible manner increasing Fibonacci numbers. Then we join the threads
and print the sorted results. One thing you immediately notice here is
that there is no intrinsic relationship between the mutex (the lock) and
the results array.
Expand Down

0 comments on commit 21b3c2f

Please sign in to comment.