update vim indent file
doc: Cleanup.

Remove ~~~ for code block specification. Use /// Over /** */ for doc
blocks.
doc: Methods for result::Result.
doc: Methods for option::Option
doc: Backticks and spelling mistakes.
doc: Remove "see above".
fix for vim < 7.4.355
Ignore two gdb tests on windows that are failing on the bots
Do not attempt to autoderef `!`

This prevents error spam when attempting to look up overload traits.
Disallow dereference of `!`

Later compiler passes are not prepared to deal with deref of
`ty_bot` and will generate various ICEs, so disallow it outright for now.

Closes issue #17373
Disallow index of `!`

This avoids ICEs in later passes that cannot cope with this construct
Add regression test for issue #17373
Add test that `!` cannot be indexed
libsyntax: Explicit error message for sugared doc comments.

Display an explicit message about items missing after sugared doc
comment attributes. References #2789.
Move bundled gcc and its libs out into $rust/rustlib/<triple>/gcc/(bin|lib).  This way the libs won't be on the -L library search path, and won't confuse external gcc, if one is used.  The bundled gcc itself will still be able to find them, because it searches for libs relative to own install location.
Prefer bundled gcc.  External gcc can still be used if one provides a full path via -Clinker=...
auto merge of #17382 : brson/rust/gdbwin, r=sfackler

Getting closer to turning on full tests.
Restore original terminal colors after error messages on Windows.
auto merge of #17218 : iliekturtles/rust/2789-invalid-doc-comment, r=huonw

Display an explicit message about items missing after sugared doc
comment attributes. References #2789.

 * I tried looking through `parser.rs` for an appropriate location for `expected_item_err` and ended up putting it just above the first use. Is there a better location?
 * Did I add enough test cases? Too many? Should I add more cases for the original error message?
Fix the span for discriminators in non-C-like enums

Fixes #17383.