Skip to content
This repository was archived by the owner on Sep 30, 2020. It is now read-only.

Commit 86ac451

Browse files
committed
Rename Debugging faq section to 'Debugging and Tooling'. Fill it out.
I particularly wanted to get the IDE question out of 'The Rust Project'.
1 parent 13bddcf commit 86ac451

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

faq.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ If there is some common or important question you feel is wrongly left unanswere
2929
<li><a href="#error-handling">Error Handling</a></li>
3030
<li><a href="#concurrency">Concurrency</a></li>
3131
<li><a href="#macros">Macros</a></li>
32-
<li><a href="#debugging">Debugging</a></li>
32+
<li><a href="#debugging">Debugging and Tooling</a></li>
3333
<li><a href="#low-level">Low-Level</a></li>
3434
<li><a href="#cross-platform">Cross-Platform</a></li>
3535
<li><a href="#modules-and-crates">Modules and Crates</a></li>
@@ -136,12 +136,6 @@ No, you cannot. Rust works hard to provide strong guarantees about the stability
136136

137137
Things stabilize all the time, and the beta and stable channels update every six weeks. If you're waiting for a feature to be available without using the nightly channel, you can locate its tracking issue by checking the [`B-unstable`](https://github.com/rust-lang/rust/issues?q=is%3Aissue+is%3Aopen+tracking+label%3AB-unstable) tag on the issue tracker.
138138

139-
<h3><a href="#what-ide-should-i-use" name="what-ide-should-i-use">
140-
What IDE should I use?
141-
</a></h3>
142-
143-
There are a number of options for development environment with Rust, all of which are detailed on the official [IDE support page](https://www.rust-lang.org/ides.html).
144-
145139
<h3><a href="#why-a-dual-mit-asl2-license" name="why-a-dual-mit-asl2-license">
146140
Why a dual MIT/ASL2 License?
147141
</a></h3>
@@ -853,7 +847,7 @@ Can I write a macro to generate identifiers?
853847

854848
Not currently. Rust macros are ["hygienic macros"](https://en.wikipedia.org/wiki/Hygienic_macro), which intentionally avoid capturing or creating identifiers that may cause unexpected collisions with other identifiers. Their capabilities are significantly different than the style of macros commonly associated with the C preprocessor. Macro invocations can only appear in places where they are explicitly supported: items, method declarations, statements, expressions, and patterns. Here, "method declarations" means a blank space where a method can be put. They can't be used to complete a partial method declaration. By the same logic, they can't be used to complete a partial variable declaration.
855849

856-
<h2 id="debugging">Debugging</h2>
850+
<h2 id="debugging">Debugging and Tooling</h2>
857851

858852
<h3><a href="#how-do-i-debug-rust-programs" name="how-do-i-debug-rust-programs">
859853
How do I debug Rust programs?
@@ -867,6 +861,18 @@ Rust programs can be debugged using [gdb](http://sourceware.org/gdb/current/onli
867861

868862
This error is usually caused by [`unwrap()`ing][unwrap] a `None` or `Err` in client code. Enabling backtraces by setting the environment variable `RUST_BACKTRACE=1` helps with getting more information. Compiling in debug mode (the default for `cargo build`) is also helpful. Using a debugger like the provided `rust-gdb` or `rust-lldb` is also helpful.
869863

864+
<h3><a href="#what-ide-should-i-use" name="what-ide-should-i-use">
865+
What IDE should I use?
866+
</a></h3>
867+
868+
There are a number of options for development environment with Rust, all of which are detailed on the official [IDE support page](https://www.rust-lang.org/ides.html).
869+
870+
<h3><a href="#wheres-rustfmt" name="wheres-rustfmt">
871+
<code>gofmt</code> is great. Where's <code>rustfmt</code>?
872+
</a></h3>
873+
874+
`rustfmt` is [right here](https://github.com/rust-lang-nursery/rustfmt), and is being actively developed to make reading Rust code as easy and predictable as possible.
875+
870876
<h2 id="low-level">Low-Level</h2>
871877

872878
<h3><a href="#how-do-i-memcpy-bytes" name="how-do-i-memcpy-bytes">
@@ -1340,12 +1346,6 @@ Rust and Go have substantially different design goals. The following differences
13401346
- Rust has strong support for generics, which Go does not.
13411347
- Rust has strong influences from the world of functional programming, including a type system which draws from Haskell's typeclasses. Go has a simpler type system, using interfaces for basic generic programming.
13421348

1343-
<h3><a href="#wheres-rustfmt" name="wheres-rustfmt">
1344-
<code>gofmt</code> is great. Where's <code>rustfmt</code>?
1345-
</a></h3>
1346-
1347-
`rustfmt` is [right here](https://github.com/rust-lang-nursery/rustfmt), and is being actively developed to make reading Rust code as easy and predictable as possible.
1348-
13491349
<h3><a href="#how-do-rust-traits-compare-to-haskell-typeclasses" name="how-do-rust-traits-compare-to-haskell-typeclasses">
13501350
How do Rust traits compare to Haskell typeclasses?
13511351
</a></h3>

0 commit comments

Comments
 (0)