about summary refs log tree commit diff
path: root/src/doc/rustc
AgeCommit message (Collapse)AuthorLines
2019-02-25Rollup merge of #55632 - ollie27:deny_overflowing_literals, r=CentrilMazdak Farrokhzad-20/+20
Deny the `overflowing_literals` lint for all editions The `overflowing_literals` was made deny by default for the 2018 edition by #54507, however I'm not aware of any reason it can't be made deny by default for the 2015 edition as well.
2019-02-20Rollup merge of #58544 - TheBiggerGuy:rustc-doc-cli-args, r=TimNNkennytm-2/+2
Fix doc for rustc "-g" flag The rustc `-g` CLI flag was miss documented to be a synonym of `-C debug-level=2` and not `-C debuglevel=2`. Also add links to the codegen docs for each synonym. I am unsure of this will conflict with work on #52938
2019-02-17Add links to codegen docs for rustc synonym flagsGuy Taylor-2/+2
The rustc "-g" and "-o" fags are synonyms of the "-c" codegen flags. This adds a link to the codegen docs for each synonym.
2019-02-17Fix doc for rustc "-g" flagGuy Taylor-1/+1
The rustc "-g" CLI flag was miss documented to be a synonym of "-C debug-level=2" and not the correct "-C debuginfo=2".
2019-02-17Mention capping forbid lintsDale Wijnand-1/+3
I felt the description of forbid was misleading/incomplete without mentioning how --cap-lints interacts with it.
2019-02-12Add documentation about -Clinker-plugin-lto to rustc book.Michael Woerister-1/+110
2019-01-18Rollup merge of #57212 - phansch:improve_rustc_book_contributing, r=steveklabnikMazdak Farrokhzad-1/+7
docs(rustc): Link to the book's source in rustc This makes the source of [the rustc book](https://doc.rust-lang.org/rustc/what-is-rustc.html) book a bit more discoverable.
2019-01-18Rollup merge of #57132 - daxpedda:master, r=steveklabnikMazdak Farrokhzad-1/+1
Document that `-C opt-level=0` implies `-C debug-assertions`. I couldn't find it stated anywhere else (https://doc.rust-lang.org/nightly/rustc/codegen-options/index.html#opt-level). It was a problem before here: https://github.com/rust-lang/rust/issues/39449, it got lost in the migration to the new documentation I assume. On a sidenote: I think that `-C opt-level=0` having a sideeffect on another flag should be changed. Having compiler flags affecting others doesn't make much sense to me, they are used to fine tune anyway. In any case, this plays no role in this PR.
2019-01-17Deny the `overflowing_literals` lint for all editionsOliver Middleton-20/+20
2019-01-03Fix repeated word typosWiktor Kuchta-13/+13
Found with `git grep -P '\b([a-z]+)\s+\1\b'`
2018-12-30docs(rustc): Link to the book's source in rustcPhilipp Hansch-1/+7
2018-12-26Document that `-C opt-level=0` implies `-C debug-assertions`.daxpedda-1/+1
2018-12-24Auto merge of #56770 - satyarohith:patch-1, r=Centrilbors-2/+2
docs(rustc): make hello() public Running the example code [here](https://doc.rust-lang.org/rustc/what-is-rustc.html#basic-usage) throws error: ``` error[E0603]: function `hello` is private --> src/main.rs:4:10 | 4 | foo::hello(); | ^^^^^ ``` Making `hello()` public fixes the problem.
2018-12-14Fixes broken linksRoberto Vidal-2/+2
2018-12-13fix: make hello publicSatya Rohith-2/+2
2018-12-13Stabilize `linker-flavor` flag.David Wood-0/+7
This commit moves the linker-flavor flag from a debugging option to a codegen option, thus stabilizing it. There are no feature flags associated with this flag.
2018-11-26rustc-guide has movedMark Mansi-2/+2
2018-10-16[Rustc Book] Quotes around value in --cfg exampleHavvy (Ryan Scheel)-1/+1
2018-10-15[Rustc Book] Explain --cfg's argumentsHavvy (Ryan Scheel)-0/+5
2018-10-14Unused result warning: "X which must" ↦ "X that must"varkor-3/+3
2018-09-08docs: Use dollar sign for all bash promptsBehnam Esfahbod-7/+10
Making it consistent across the board, as most of them already use `$`. Also split one continues bash run into two, to make it easier see different runs: one with warning and another with error.
2018-09-07Rollup merge of #53550 - brson:recurring, r=estebankkennytm-2/+2
librustc_lint: In recursion warning, change 'recurring' to 'recursing' The existing wording seems incorrect. Aside: This warning, 'function cannot return without recursing' is not perfectly clear - it implies that the function _can_ return, it's just got to recurse. But really the fn cannot return period. Clearer wording: 'function recurses infinitely; it cannot return'; or 'function is infinitely self-recursive; it cannot return, and this is probably an error'. I like that.
2018-08-20librustc_lint: In recursion warning, change 'recurring' to 'recursing'Brian Anderson-2/+2
2018-08-19Fix typos found by codespell.Matthias Krüger-3/+3
2018-05-25Fix naming conventions for new lintsVadim Petrochenkov-1/+1
2018-05-15Turn deprecation lint `legacy_imports` into a hard errorVadim Petrochenkov-37/+0
2018-05-03ignore erroneous exampleHoàng Đức Hiếu-1/+1
2018-05-03fix error textHoàng Đức Hiếu-1/+1
2018-05-03doc: move incoherent_fundamental_impls to deny-by-default listingHoàng Đức Hiếu-41/+41
2018-04-24more nitssteveklabnik-3/+3
2018-04-23review nitssteveklabnik-9/+8
2018-04-16write docs for targetssteveklabnik-0/+38
2018-04-16fill out contributingsteveklabnik-0/+5
2018-04-16fill out command line argumentssteveklabnik-2/+61
2018-04-10add codegen options sectionsteveklabnik-0/+208
2018-04-09fix testssteveklabnik-27/+29
2018-04-09more lintssteveklabnik-46/+1035
2018-04-09document deny by default lintssteveklabnik-12/+237
2018-04-09add a lot of text about lintssteveklabnik-0/+824
2018-04-09add targets to TOCsteveklabnik-0/+6
2018-04-09write 'what is rustc'steveklabnik-0/+67
2018-04-09write headings for command line argumentssteveklabnik-2/+58
2018-04-09fix authorship in book.tomlsteveklabnik-1/+1
2018-04-09Add a TOCsteveklabnik-3/+23
2018-04-09initialize the rustc booksteveklabnik-0/+10
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-23 02:15:11 +0000