- 08 4月, 2015 24 次提交
-
-
由 Alex Crichton 提交于
It's somewhat common to impl traits for `&T` and `&mut T` so show these on the pages for `T` to ensure they're listed somewhere at least. Closes #20175
-
由 Alex Crichton 提交于
This renders a "Methods" and "Trait Implementations" section for each item implemented for a bare trait itself. Closes #19055
-
由 Alex Crichton 提交于
Allow a few specific ones but otherwise this helps ensure that our examples are squeaky clean! Closes #18199
-
由 Alex Crichton 提交于
This adds support in rustdoc to blanket apply crate attributes to all doc tests for a crate at once. The syntax for doing this is: #![doc(test(attr(...)))] Each meta item in `...` will be applied to each doctest as a crate attribute. cc #18199
-
由 Alex Crichton 提交于
All methods listed in "Trait Implementations" now hyperlink to the source trait instead of themselves, allowing easy browsing of the documentation of a trait method. Closes #17476
-
由 Alex Crichton 提交于
If an empty public module has no documentation, it shouldn't emit a page that's just a redirect loop to itself! Closes #16265
-
由 Alex Crichton 提交于
Closes #16019
-
由 Alex Crichton 提交于
Closes #15347
-
由 Alex Crichton 提交于
Closes #15318
-
由 Alex Crichton 提交于
This ensures that def ids don't drift too much over time. Closes #15309
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
This ensures that all external traits are run through the same filters that the rest of the AST goes through, stripping hidden function as necessary. Closes #13698
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
Add a new test directory called 'rustdoc' where all files inside are documented and run against the `htmldocck` script to have assertions about the output.
-
由 bors 提交于
- Successful merges: #24132, #24139, #24147, #24148, #24150, #24166 - Failed merges:
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
This fix allows the gdb debuginfo tests to pass on FreeBSD when using the newer 7.8 package.
-
由 Manish Goregaokar 提交于
People use programming language *implementations* like Ruby MRI, CPython, and SpiderMonkey for executing programs.
-
由 Manish Goregaokar 提交于
Closes #22560
-
由 Manish Goregaokar 提交于
Use HTTPS where possible to avoid plaintext HTTP connections.
-
由 Manish Goregaokar 提交于
@mahkoh points out in #15628 that unicode.py does not use normative data for Grapheme classes. This pr fixes that issue, and does some minor cleanup of the unicode.py script. In addition, GC_RegionalIndicator is renamed GC_Regional_Indicator in order to stay in line with the Unicode class name definitions. I have updated refs in u_str.rs, and verified that there are no refs elsewhere in the codebase. However, in principle someone using the unicode tables for their own purposes might see breakage from this.
-
由 Tero Hänninen 提交于
-
由 bors 提交于
-
由 Manish Goregaokar 提交于
-
- 07 4月, 2015 16 次提交
-
-
由 Manish Goregaokar 提交于
* Fix broken \"module-level documentation\" link on the [`trait Any` docs](http://doc.rust-lang.org/std/any/trait.Any.html) and related broken markup on the [`std::any` docs](http://doc.rust-lang.org/std/any/index.html). * Remove an outdated or incorrect notice in the `BufRead::lines` docs. There is no such `read_string` function, and `lines` never returns an error. r? @steveklabnik
-
由 Manish Goregaokar 提交于
traits.md said: If we add a `use` line right above `main` and make the right things public, everything is fine: However, the use line was actually placed at the top of the file instead. Move the use line to right above main. That also makes the example more evocative of cases where the module is defined in a separate file.
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
Fixes #24060.
-
由 Manish Goregaokar 提交于
This probably needs a bit more work, but I wanted to try and capture some common use cases and be a bit more helpful. r? @huonw cc @steveklabnik
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
Fixes #24030 Of the four code samples with modules in TRPL: - 2 use `mod test` - 2 use `mod tests` We should be consistent here, but which is right? The stdlib is split: $ grep -r 'mod tests {' src/lib* | wc -l 63 $ grep -r 'mod test {' src/lib* | wc -l 58 Subjectively, I like the plural, but both the language reference and the style guide recommend the singular. So we'll go with that here, for now. r? @steveklabnik
-
由 Manish Goregaokar 提交于
cc @steveklabnik
-
由 Luke Gallagher 提交于
-
由 Will 提交于
-
由 bors 提交于
cc @steveklabnik
-
由 Xue Fuqiao 提交于
People use programming language *implementations* like Ruby MRI, CPython, and SpiderMonkey for executing programs.
-
由 Luke Gallagher 提交于
Closes #22560
-
由 bors 提交于
Because the current style for `code` in rustdoc is to prewrap whitespace, code spans that are hard wrapped in the source documentation are prematurely wrapped when rendered in HTML. [For example][2], ``` /// ... /// type can be borrowed as multiple different types. In particular, `Vec<T>: /// Borrow<Vec<T>>` and `Vec<T>: Borrow<[T]>`. ``` renders as ![screen shot 2015-04-06 at 12 11 21](https://cloud.githubusercontent.com/assets/191331/7008216/2706b3b0-dc56-11e4-941e-1b0154fcbc5c.png) because "`Vec<T>: Borrow<Vec<T>>`" wraps to the next line in the source. CommonMark 0.18 [[1]] specifies "interior spaces and line endings are collapsed into single spaces" for code spans, which would actually prevent this issue, but hoedown does not currently conform to the CommonMark spec. The added span-level callback attempts to adhere to how whitespace is handled as described by CommonMark, fixing the issue of early, unintentional wrapping of code spans in rendered HTML. [1]: http://spec.commonmark.org/0.18/ [2]: https://doc.rust-lang.org/std/borrow/trait.Borrow.html
-
由 Xue Fuqiao 提交于
Use HTTPS where possible to avoid plaintext HTTP connections.
-
由 bors 提交于
The current help string ("space separated list") suggests that `--passes "pass1 pass2"` is expected; the orrect usage is `--passes pass1 --passes pass2`.
-