- 03 6月, 2014 9 次提交
-
-
由 bors 提交于
-
由 bors 提交于
I've been working around these parts of code and it seems like it could use a bit of a refactor. This is the first step.
-
由 bors 提交于
Now that rustdoc understands proper language tags as the code not being Rust, we can tag everything properly. `norust` as a negative statement is a bad tag. This change tags examples in other languages by their language. Plain notations are marked as `text`. Console examples are marked as `console`. Also fix markdown.rs to not highlight non-rust code. Amends the documentation to reflect the new behaviour.
-
由 bors 提交于
Closes #10764
-
由 Aaron Turon 提交于
-
由 bors 提交于
This patchset removes `pub use` usage except for `test/`. cc #11870
-
由 Jakub Wieczorek 提交于
-
由 Jakub Wieczorek 提交于
-
由 Alex Crichton 提交于
Closes #10764
-
- 02 6月, 2014 11 次提交
-
-
由 klutzy 提交于
`quote_expr!` now injects two more (priv) `use` globs. This may cause extra unused_imports warning.
-
由 klutzy 提交于
-
由 Florian Gilcher 提交于
Now that rustdoc understands proper language tags as the code not being Rust, we can tag everything properly. This change tags examples in other languages by their language. Plain notations are marked as `text`. Console examples are marked as `console`. Also fix markdown.rs to not highlight non-rust code.
-
由 bors 提交于
Closes #14021
-
由 Piotr Jawniak 提交于
Closes #14021
-
由 bors 提交于
This changes the parsing of the language string in code examples so that unrecognized examples are not considered Rust code. This was, for example, the case when a code example was marked `sh` for shell code. This relieves authors of having to mark those samples as `notrust`. Also adds recognition of the positive marker `rust`. By default, unmarked examples are still considered rust.
-
由 bors 提交于
Fixes #9205.
-
由 klutzy 提交于
Fixes #9205.
-
由 Florian Gilcher 提交于
This changes the parsing of the language string in code examples so that unrecognized examples are not considered Rust code. This was, for example, the case when a code example was marked `sh` for shell code. This relieves authors of having to mark those samples as `notrust`. Also adds recognition of the positive marker `rust`. By default, unmarked examples are still considered rust. If any rust-specific tags are seen, code is considered rust unless marked as "notrust". Adds test cases for the detection logic.
-
由 bors 提交于
This completes the last stage of the renaming of the comparison hierarchy of traits. This change renames TotalEq to Eq and TotalOrd to Ord. In the future the new Eq/Ord will be filled out with their appropriate methods, but for now this change is purely a renaming change. This continues the work of #12517, continuing the work in #14534. This patch accomplishes the final rename of `TotalEq` to `TotalOrd`. I wanted to get this patch landed ASAP so we don't have to deal much with "where did `Eq` and `Ord` go?" I have yet to do another pruning pass over the compiler to change all usage of `PartialEq` to `Eq` where appropriate. I will do this soon as well.
-
由 Alex Crichton 提交于
This completes the last stage of the renaming of the comparison hierarchy of traits. This change renames TotalEq to Eq and TotalOrd to Ord. In the future the new Eq/Ord will be filled out with their appropriate methods, but for now this change is purely a renaming change. [breaking-change]
-
- 01 6月, 2014 20 次提交
-
-
由 bors 提交于
`reader.read_line()` includes trailing newline char, which makes `from_str` always return `None`.
-
由 bors 提交于
doc: add an `.as_slice` example to the cheatsheet. A lot of questions about this on IRC and stackoverflow.
-
由 bors 提交于
Fixes #14570.
-
由 Utkarsh Kukreti 提交于
`reader.read_line()` includes trailing newline char, which makes `from_str` always return `None`.
-
由 bors 提交于
This is currently rebased on top of #14478, but that's just to preemptively avoid rebase conflicts and to provide a better preview. This can land independently of that PR. This change crates a dedicated page in rustdoc for primitive types to outline everything you can do with them (at least in a basic way). * Preview - http://people.mozilla.org/~acrichton/doc/ * Exhibit A - http://people.mozilla.org/~acrichton/doc/std/#primitives * Exhibit B - http://people.mozilla.org/~acrichton/doc/std/primitive.str.html * Exhibit C - http://people.mozilla.org/~acrichton/doc/std/primitive.slice.html Please don't hesitate to be nitpickity, it's easy to overlook a thing here or there!
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
These don't actually point to anything, so there's no need to inline them.
-
由 Alex Crichton 提交于
Cross crate links can target items which are not rendered in the documentation. If the item is reexported at a higher level, the destination of the link (a concatenation of the fully qualified name) may actually lead to nowhere. This fixes this problem by altering rustdoc to emit pages which redirect to the local copy of the reexported structure. cc #14515 Closes #14137
-
由 Alex Crichton 提交于
cc #14515
-
由 Alex Crichton 提交于
There is currently no way to query all impls for a type from an external crate, and with primitive types in play this is also quite difficult. Instead of filtering, just suck in all impls from upstream crates into the local AST, and have them get stripped later. This will allow population of all implementations of traits for primitive types, as well as filling in some corner cases with inlining documentation in other cases.
-
由 Alex Crichton 提交于
This prevents structures like RcBox from showing up in the documentation
-
由 Alex Crichton 提交于
This commit adds support in rustdoc to recognize the `#[doc(primitive = "foo")]` attribute. This attribute indicates that the current module is the "owner" of the primitive type `foo`. For rustdoc, this means that the doc-comment for the module is the doc-comment for the primitive type, plus a signal to all downstream crates that hyperlinks for primitive types will be directed at the crate containing the `#[doc]` directive. Additionally, rustdoc will favor crates closest to the one being documented which "implements the primitive type". For example, documentation of libcore links to libcore for primitive types, but documentation for libstd and beyond all links to libstd for primitive types. This change involves no compiler modifications, it is purely a rustdoc change. The landing pages for the primitive types primarily serve to show a list of implemented traits for the primitive type itself. The primitive types documented includes both strings and slices in a semi-ad-hoc way, but in a way that should provide at least somewhat meaningful documentation. Closes #14474
-
由 Alex Crichton 提交于
Type parameters were filled in for some areas, but not all. This commit unifies the two code paths to fill in type parameters everywhere. Closes #14508
-
由 Alex Crichton 提交于
cc #14462
-
由 Alex Crichton 提交于
When inlining documentation across crates, primitive implementors of traits were not shown. This commit tweaks the infrastructure to treat primitive and Path-like impls the same way, displaying all implementors everywhere. cc #14462
-
由 Alex Crichton 提交于
The cache is going to be used earlier in the HTML generation process, which means that it needs to get into TLS as soon as possible.
-
由 Alex Crichton 提交于
Instead of one giant function, this breaks it up into several smaller functions which have explicit dependencies among one another. There are no code changes as a result of this commit.
-
由 bors 提交于
Fixes #11319
-
由 Huon Wilson 提交于
A lot of questions about this on IRC and stackoverflow.
-
由 bors 提交于
This rewrites the example to also be more aligned with the same example given in the main tutorial.
-