Skip to content

Commit 34c39bb

Browse files
committed
Rewrited section about rust tool
1 parent 8ee2d58 commit 34c39bb

File tree

1 file changed

+8
-11
lines changed

1 file changed

+8
-11
lines changed

doc/tutorial.md

+8-11
Original file line numberDiff line numberDiff line change
@@ -162,17 +162,14 @@ running them manually is a perfectly valid way to test your code,
162162
for smaller projects, prototypes, or if you're a beginner, it might be
163163
more convenient to use the `rust` tool.
164164

165-
You use it by calling it with one of the supported commands, followed by
166-
arguments for that command. For example `rust build foo.rs` calls the
167-
`build` command with the argument `foo.rs`.
168-
169-
The commands are:
170-
- `build`, `doc`, `pkg` and `sketch`, which simply forward all arguments
171-
to the included programs `rustc`, `rustdoc`, `rustpkg` and `rusti`.
172-
- `run` and `test`, which both accept one source file and, using `rustc`,
173-
produce either a normal or a test executable in the current working
174-
directory and run it.
175-
- `help`, which prints out the usage text of one of the commands.
165+
The `rust` tool provides central access to the other rust tools,
166+
as well as handy shortcuts for directly running source files.
167+
For example, if you have a file `foo.rs` in your current directory,
168+
`rust run foo.rs` would attempt to compile it and, if successful,
169+
directly run the resulting binary.
170+
171+
To get a list of all available commands, simply call `rust` without any
172+
argument.
176173

177174
## Editing Rust code
178175

0 commit comments

Comments
 (0)