| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2018-09-10 | [beta] rustdoc: disable blanket impl collection | QuietMisdreavus | -111/+2 | |
| 2018-07-30 | Delete unused code in rustdoc | Mark Rousskov | -22/+0 | |
| 2018-07-29 | Remove unused `mut`s | Matthew Jasper | -1/+1 | |
| 2018-07-28 | Auto merge of #52585 - GuillaumeGomez:generic-impls, r=QuietMisdreavus | bors | -28/+148 | |
| [rustdoc] Generic impls Fixes #33772. r? @QuietMisdreavus | ||||
| 2018-07-28 | Move blanket implementations generation into its own function | Guillaume Gomez | -19/+29 | |
| 2018-07-28 | Remove core exclusion condition | Guillaume Gomez | -13/+13 | |
| 2018-07-28 | Don't display full blanket implementation and put it into its own section | Guillaume Gomez | -2/+8 | |
| 2018-07-25 | Add missing dyn | Tatsuyuki Ishi | -1/+1 | |
| 2018-07-24 | Remove generic-impl rendering filter | Guillaume Gomez | -85/+83 | |
| 2018-07-24 | Add src and fix generics display issues | Guillaume Gomez | -6/+6 | |
| 2018-07-23 | Auto merge of #52211 - bjorn3:misc_rustdoc_changes, r=QuietMisdreavus | bors | -8/+0 | |
| Misc rustdoc changes | ||||
| 2018-07-23 | Fix style issues | Guillaume Gomez | -7/+9 | |
| 2018-07-22 | Fix urls | Guillaume Gomez | -4/+4 | |
| 2018-07-22 | Prevent some items to get generic impls listed | Guillaume Gomez | -1/+2 | |
| 2018-07-22 | Improve code | Guillaume Gomez | -54/+43 | |
| 2018-07-22 | Add new tests and fix old ones | Guillaume Gomez | -37/+65 | |
| 2018-07-22 | Cleanup | Guillaume Gomez | -59/+1 | |
| 2018-07-22 | Add filter over non generic impls | Guillaume Gomez | -53/+38 | |
| 2018-07-22 | Working generic impl | Guillaume Gomez | -114/+171 | |
| 2018-07-22 | some improvements | Guillaume Gomez | -3/+8 | |
| 2018-07-22 | part 2 | Guillaume Gomez | -58/+41 | |
| 2018-07-22 | First step to generic trait impls | Guillaume Gomez | -20/+113 | |
| 2018-07-22 | Start of generic impl fix for rustdoc | Guillaume Gomez | -3/+24 | |
| 2018-07-23 | Rollup merge of #52581 - petrochenkov:bmacrodoc, r=alexcrichton | kennytm | -7/+5 | |
| Avoid using `#[macro_export]` for documenting builtin macros Use a special `rustc_*` attribute instead. cc https://github.com/rust-lang/rust/pull/52234 | ||||
| 2018-07-22 | Auto merge of #52368 - ↵ | bors | -2/+59 | |
| GuillaumeGomez:intra_doc_link_resolution_failure-documented, r=QuietMisdreavus Add "self" intra-link support Fixes #49583. r? @QuietMisdreavus | ||||
| 2018-07-22 | Add "self" intra-link support | Guillaume Gomez | -2/+59 | |
| 2018-07-21 | Avoid using `#[macro_export]` for documenting builtin macros | Vadim Petrochenkov | -7/+5 | |
| 2018-07-19 | Auto merge of #52024 - oli-obk:existential_parse, r=nikomatsakis | bors | -0/+32 | |
| Implement existential types (not for associated types yet) r? @nikomatsakis cc @Centril @varkor @alexreg | ||||
| 2018-07-19 | Auto merge of #51854 - davidtwco:rfc-2008-rustdoc, r=QuietMisdreavus | bors | -0/+5 | |
| RFC 2008 non-exhaustive enums/structs: Rustdoc Part of #44109. Not sure how those who maintain rustdoc primarily would prefer this addition look or where it should be placed, happy to make any changes required. r? @QuietMisdreavus (not sure if this is the right person, just guessing) | ||||
| 2018-07-18 | Implement existential types | Oliver Schneider | -0/+32 | |
| 2018-07-16 | ItemKind | csmoe | -24/+25 | |
| 2018-07-16 | ForeignItemKind | csmoe | -3/+3 | |
| 2018-07-16 | TyKind | csmoe | -3/+3 | |
| 2018-07-15 | Auto merge of #52361 - QuietMisdreavus:proc-macro-doc, r=ollie27 | bors | -5/+9 | |
| rustdoc: don't panic when the cross-re-export handler sees a proc-macro When i moved the macro cross-re-export inlining code into `clean::inline`, i thought that if a macro had a `Def` that said it was a bang macro, it wouldn't be a proc macro. I thought wrong. Turns out, the `quote!()` in `libproc_macro` is actually a proc-macro, and when the `quote!()` macro is re-exported, this proc-macro is accessed in its place. This causes any `proc_macro::*` glob re-export to pull in this proc-macro, causing the assertion i added to fire, leading to an ICE. This replaces that with an Option that ignores proc-macros for the time being. Fixes https://github.com/rust-lang/rust/issues/52129 | ||||
| 2018-07-14 | Address comments | Vadim Petrochenkov | -3/+1 | |
| 2018-07-14 | Remove most of `Hash` impls from AST and HIR structures | Vadim Petrochenkov | -2/+15 | |
| 2018-07-14 | Remove most of `PartialEq` impls from AST and HIR structures | Vadim Petrochenkov | -2/+16 | |
| 2018-07-13 | don't panic when you see proc-macros | QuietMisdreavus | -5/+9 | |
| 2018-07-13 | Misc rustdoc changes | bjorn3 | -8/+0 | |
| 2018-07-13 | Switch to any from count when checking for non_exhaustive attribute. | David Wood | -2/+1 | |
| 2018-07-05 | Simplified checking for non_exhaustive attribute. | David Wood | -28/+6 | |
| 2018-07-04 | Auto merge of #51611 - QuietMisdreavus:slippery-macros, r=ollie27 | bors | -5/+38 | |
| rustdoc: import cross-crate macros alongside everything else The thrilling conclusion of the cross-crate macro saga in rustdoc! After https://github.com/rust-lang/rust/pull/51425 made sure we saw all the namespaces of an import (and prevented us from losing the `vec!` macro in std's documentation), here is the PR to handle cross-crate macro re-exports at the same time as everything else. This way, attributes like `#[doc(hidden)]` and `#[doc(no_inline)]` can be used to control how the documentation for these macros is seen, rather than rustdoc inlining every macro every time. Fixes https://github.com/rust-lang/rust/issues/50647 | ||||
| 2018-07-02 | Update rustdoc | Oliver Schneider | -8/+0 | |
| 2018-07-01 | call it `hir::VisibilityKind` instead of `hir::Visibility_:*` | Zack M. Davis | -4/+4 | |
| It was pointed out in review that the glob-exported underscore-suffixed convention for `Spanned` HIR nodes is no longer preferred: see February 2016's #31487 for AST's migration away from this style towards properly namespaced NodeKind enums. This concerns #51968. | ||||
| 2018-06-30 | in which hir::Visibility recalls whence it came (i.e., becomes Spanned) | Zack M. Davis | -8/+8 | |
| There are at least a couple (and plausibly even three) diagnostics that could use the spans of visibility modifiers in order to be reliably correct (rather than hacking and munging surrounding spans to try to infer where the visibility keyword must have been). We follow the naming convention established by the other `Spanned` HIR nodes: the "outer" type alias gets the "prime" node-type name, the "inner" enum gets the name suffixed with an underscore, and the variant names are prefixed with the prime name and `pub use` exported from here (from HIR). Thanks to veteran reviewer Vadim Petrochenkov for suggesting this uniform approach. (A previous draft, based on the reasoning that `Visibility::Inherited` should not have a span, tried to hack in a named `span` field on `Visibility::Restricted` and a positional field on `Public` and `Crate`. This was ... not so uniform.) | ||||
| 2018-06-30 | Fortify dummy span checking | Vadim Petrochenkov | -1/+1 | |
| 2018-06-30 | expansion: Give names to some fields of `SyntaxExtension` | Vadim Petrochenkov | -1/+1 | |
| 2018-06-28 | Rollup merge of #51636 - oli-obk:const_diagnostics, r=eddyb | Mark Rousskov | -4/+4 | |
| Refactor error reporting of constants cc @eddyb This PR should not change any behaviour. It solely simplifies the internal handling of the errors | ||||
| 2018-06-28 | Merge `ConstVal` and `ConstValue` | Oliver Schneider | -4/+4 | |
| 2018-06-28 | Move everything over from `middle::const_val` to `mir::interpret` | Oliver Schneider | -1/+1 | |
 |
index : rust | |
| https://github.com/rust-lang/rust |
| summary refs log tree commit diff |