summary refs log tree commit diff
path: root/src/librustdoc/clean
AgeCommit message (Collapse)AuthorLines
2019-04-26rustdoc: Remove default keyword from re-exported trait methodsOliver Middleton-1/+5
2019-04-06Rollup merge of #58894 - GuillaumeGomez:invalid-lifetime-bounds, r=estebankMazdak Farrokhzad-10/+10
Fix invalid bounds string generation in rustdoc Fixes #58737. Very weird and I'm not sure this is the best fix around. However, trying to fix it beforehand seems overly complicated compared to the gain (in `clean`, it wouldn't change anything since we **have to** return something so that wouldn't work, and in `hir`, I'm afraid I'd break something else for very little gain). Also, I wasn't able to make a small code to reproduce the issue. The only way to test is to document `crossbeam` directly and check the `Scope` struct... r? @QuietMisdreavus
2019-03-31Fix invalid bounds string generation in rustdocGuillaume Gomez-10/+10
2019-03-30Rollup merge of #59539 - GuillaumeGomez:rustdoc-infinite-recursion, r=eddybMazdak Farrokhzad-5/+9
Fix infinite recursion Temporary fix for #59502. r? @eddyb
2019-03-30Fix infinite recursionGuillaume Gomez-5/+9
2019-03-30Rollup merge of #59376 - davidtwco:finally-rfc-2008-variants, ↵Mazdak Farrokhzad-0/+3
r=petrochenkov,QuietMisdreavus RFC 2008: Enum Variants Part of #44109. See [Zulip topic](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/rfc-2008/near/132663140) for previous discussion. r? @petrochenkov cc @nikomatsakis
2019-03-29Support non-exhaustive enum variants in rustdoc.David Wood-0/+3
This commit adds support for non-exhaustive enum variants in rustdoc, extending the existing support for non-exhaustive enums and structs.
2019-03-28Rollup merge of #59413 - Zoxc:hirid, r=oli-obkMazdak Farrokhzad-9/+9
HirIdify hir::ItemId Version of https://github.com/rust-lang/rust/pull/59092. r? @oli-obk
2019-03-26Rollup merge of #59004 - GuillaumeGomez:generics-handling, r=QuietMisdreavusGuillaume Gomez-10/+196
[rustdoc] Improve "in parameters" search and search more generally Fixes #58230. r? @QuietMisdreavus
2019-03-25hir: replace NodeId with HirId in ItemIdljedrz-9/+9
2019-03-24Remove `VariantDef::parent_did`Vadim Petrochenkov-6/+5
2019-03-24Remove methods is_struct/is_tuple/is_unit from VariantDataVadim Petrochenkov-6/+5
2019-03-24Separate variant id and variant constructor id.David Wood-9/+8
This commit makes two changes - separating the `NodeId` that identifies an enum variant from the `NodeId` that identifies the variant's constructor; and no longer creating a `NodeId` for `Struct`-style enum variants and structs. Separation of the variant id and variant constructor id will allow the rest of RFC 2008 to be implemented by lowering the visibility of the variant's constructor without lowering the visbility of the variant itself. No longer creating a `NodeId` for `Struct`-style enum variants and structs mostly simplifies logic as previously this `NodeId` wasn't used. There were various cases where the `NodeId` wouldn't be used unless there was an unit or tuple struct or enum variant but not all uses of this `NodeId` had that condition, by removing this `NodeId`, this must be explicitly dealt with. This change mostly applied cleanly, but there were one or two cases in name resolution and one case in type check where the existing logic required a id for `Struct`-style enum variants and structs.
2019-03-23Add testGuillaume Gomez-21/+15
2019-03-23cleanupGuillaume Gomez-10/+18
2019-03-22Rollup merge of #59170 - varkor:const-generics-rustdoc, r=QuietMisdreavus,eddybMazdak Farrokhzad-82/+114
Add const generics to rustdoc Split out from #53645. This work is a collaborative effort with @yodaldevoid. The `FIXME`s are waiting on a refactor to `LazyConst`. I'll address these in a follow up, but I thought it would be better to implement the rest now to avoid bitrot. r? @QuietMisdreavus
2019-03-21Fix invalid returned types generationGuillaume Gomez-40/+40
2019-03-21Add bounds for return types as wellGuillaume Gomez-9/+35
2019-03-21Improve bounds searchGuillaume Gomez-48/+6
2019-03-21Greatly improve generics handling in rustdoc searchGuillaume Gomez-10/+210
2019-03-21Auto merge of #58927 - GuillaumeGomez:default-keyword, r=QuietMisdreavusbors-4/+20
Add default keyword handling in rustdoc Fixes #58898. r? @QuietMisdreavus
2019-03-18Rebase over LazyConst changesvarkor-11/+1
2019-03-18Rename first_ty_sty to ty_styvarkor-4/+4
2019-03-18Refactor `GenericArgs` to include const genericsvarkor-59/+65
Co-Authored-By: Gabriel Smith <yodaldevoid@users.noreply.github.com>
2019-03-18Add `GenericArg`varkor-0/+17
Co-Authored-By: Gabriel Smith <yodaldevoid@users.noreply.github.com>
2019-03-18Implement `Clean` for const genericsvarkor-0/+19
Co-Authored-By: Gabriel Smith <yodaldevoid@users.noreply.github.com>
2019-03-18Rename external_typarams to external_param_namesvarkor-2/+2
Co-Authored-By: Gabriel Smith <yodaldevoid@users.noreply.github.com>
2019-03-18Rename typarams to param_namesvarkor-20/+20
Co-Authored-By: Gabriel Smith <yodaldevoid@users.noreply.github.com>
2019-03-17Auto merge of #59178 - oli-obk:lazy_const, r=eddybbors-8/+8
Revert the `LazyConst` PR The introduction of `LazyConst` did not actually achieve the code simplicity improvements that were the main reason it was introduced. Especially in the presence of const generics, the differences between the "levels of evaluatedness" of a constant become less clear. As it can be seen by the changes in this PR, further simplifications were possible by folding `LazyConst` back into `ConstValue`. We have been able to keep all the advantages gained during the `LazyConst` refactoring (like `const_eval` not returning an interned value, thus making all the `match` code simpler and more performant). fixes https://github.com/rust-lang/rust/issues/59209 r? @eddyb @varkor
2019-03-16Refactor away `NestedMetaItemKind`Vadim Petrochenkov-10/+10
Remove methods `Attribute::span` and `MetaItem::span` duplicating public fields
2019-03-16Rename `MetaItem::ident` to `MetaItem::path`Vadim Petrochenkov-5/+5
2019-03-16syntax: Do not accidentally treat multi-segment meta-items as single-segmentVadim Petrochenkov-4/+10
2019-03-16Revert the `LazyConst` PROliver Scherer-8/+8
2019-03-15rustc: provide DisambiguatedDefPathData in ty::print.Eduard-Mihai Burtescu-2/+4
2019-03-15rustc: slice substs in ty::print instead of passing the full ones.Eduard-Mihai Burtescu-1/+1
2019-03-15rustc: remove PrintCx from ty::Print and rely on printers carrying TyCtxt.Eduard-Mihai Burtescu-27/+30
2019-03-15rustc: don't thread existential projections through path_generic_args.Eduard-Mihai Burtescu-4/+11
2019-03-15rustc: make `pretty_path_generic_args`' task as simple as possible.Eduard-Mihai Burtescu-3/+2
2019-03-15rustc: move ty::print::PrintConfig's fields to FmtPrinter.Eduard-Mihai Burtescu-3/+3
2019-03-15rustc: don't pass Namespace explicitly, but rather track it in FmtPrinter.Eduard-Mihai Burtescu-4/+2
2019-03-15rustc: support overriding type printing in ty::print::Printer.Eduard-Mihai Burtescu-0/+8
2019-03-15rustc: support overriding region printing in ty::print::Printer.Eduard-Mihai Burtescu-0/+8
2019-03-15rustc: pass ty::print::PrintCx by value.Eduard-Mihai Burtescu-17/+37
2019-03-15rustc: split off most of ty::print::PrintCx's fields into a separate struct.Eduard-Mihai Burtescu-3/+3
2019-03-15rustc: uniformize ty::print's error handling by requiring Result.Eduard-Mihai Burtescu-9/+15
2019-03-15rustc: move `...::<impl ...>` printing into `pretty_path_qualified`.Eduard-Mihai Burtescu-2/+7
2019-03-15rustc: move <...>-less impl path special-case to pretty_path_qualified.Eduard-Mihai Burtescu-3/+1
2019-03-15rustc: merge PrintCx::parameterized and def_path printing.Eduard-Mihai Burtescu-2/+24
2019-03-15rustc: move the contents of ty::item_path to ty::print.Eduard-Mihai Burtescu-3/+2
2019-03-15rustc: rename item_path to def_path (except the module in ty).Eduard-Mihai Burtescu-1/+1
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-14 03:54:15 +0000