Create an ebook for the Docs.

References this tweet

Suggested tool: mdbook

I'm not sure if it was deliberately left blank or not. The markdown has nothing in it. Maybe it accidentally got left off?

I came here looking for the equivalent for python's range/xrange step parameter. I later discovered .step_by(). An example like the following would have helped me:

python:

for i in range(0,10,2):
   print i # 0, 2, 4, 6, 8

rust:

for i in (0..10).step_by(2) {
    println('{}', i);  // 0, 2, 4, 6, 8
}

Hello, there is a scope of improvement in the README.md file along with fixing a few grammatical errors. I would like to work on it.

Could you please assign this to me?

I suggest put 2D/3D engine Bevy is very popular

Given that Rust uses modified Hindley-Milner type inference, that line shouldn't mention Python or Ruby, but rather ML and Haskell.

http://www.exercism.io/languages/rust/about is now inaccessible.

Instead, the following url works.
http://www.exercism.io/languages/rust/

Reading through the document, I noticed (particularly in Rust) use of language features that aren't explained and code examples for the other language aren't trivial.

Examples

• Rust macros
• Rust Implicit returns

I found it a little confusing to read through all the examples in the README file. Perhaps if it were organized by topics in the examples folder it would be easier and more intuitive for beginners to learn. Like the following structure:

.
└── examples/
├── hello_world/
│ ├── main.py
│ └── main.rs
├── types/
│ ├── main.py
│ └── main.rs
└── lists/
├── main.py
└── main.rs

There’s extra output in the Rust example, and I believe the Rust example is creating a thread whereas the python example is not (although it could be implicit as I’m not familiar with Queue)

1. Aren't Crossbeam and Rayon libraries about threads? They doesn't seem to match the description "Run external commands".

2. The python code of derive_new crate __init__(self, value='default') kind of suggest that rust has optional parameters, which rust does not.

Meh.
Please update the ReadMe.

The currently listed equivalent to python's numpy is numeric which has last received an update in 2016 and seems to be dropping in popularity rapidly.

I'd suggest the alternative crate ndarray.

Additionally, there is also the numpy crate which can be used to more easily create rust libs for python via pyo3.

Great job, Bruno! Nice to know you're into Rust now - I'm barely starting to learn it :-)

So, one issue I found in the listing of libraries is the mention for mockito; now, although the homonimous Java library is indeed a proper general mocking library, Rust's mockito only really mocks HTTP services, and not structs or methods. Which is a bit sad - I expected more from that library when I saw that name.

Therefore I think it should not be in the list as a Rust alternative to Python's mock library - which is a general-purpose mocking library (now integrated into Python 3).

Cheers!
Diogo

old URL
http://rustbyexample.com

new URL
https://doc.rust-lang.org/stable/rust-by-example/

Cool project. I think this might help many people. However, I think a few things here are misleading or could be improved:

• https://github.com/BurntSushi/quickcheck is much more developed and maintained than proptest.
• http://ggez.rs/ is probably more like pygame in that it comes batteries included.
• Gotham really is not at all a contender to Django. There is nothing there for Django so far.
• The link to fs is incorrect.

Maybe it would also be good to list python packages that have no direct equivalent yet (such as Django) so that people know what they're getting into?