Browsing French translation

1.

% How to submit a Rust bug report

2.

# I think I found some bugs in rustc compiler!

3.

If you see this message: `error: internal compiler error: unexpected failure`, then you have definitely found a bug in the compiler. It's also possible that your code is not well-typed, but if you saw this message, it's still a bug in error reporting.

4.

If you see a message about an LLVM assertion failure, then you have also definitely found a bug in the compiler. In both of these cases, it's not your fault and you should report a bug!

5.

If you see a compiler error message that you think is meant for users to see, but it confuses you, *that's a bug too*. If it wasn't clear to you, then it's an error message we want to improve, so please report it so that we can try to make it better.

6.

Liigo add this line. 1.

7.

# How do I know the bug I found isn't a bug that already exists in the issue tracker?

8.

If you don't have enough time for a search, then don't worry about that. Just submit the bug. If it's a duplicate, somebody will notice that and close it during triage.

9.

If you have the time for it, it would be useful to type the text of the error message you got [into the issue tracker search box](https://github.com/rust-lang/rust/issues) to see if there's an existing bug that resembles your problem. If there is, and it's an open bug, you can comment on that issue and say you are also affected. This will encourage the devs to fix it. But again, don't let this stop you from submitting a bug. We'd rather have to do the work of closing duplicates than miss out on valid bug reports.

10.

Liigo add this line. 2.