summary refs log tree commit diff
path: root/src/librustdoc/html
AgeCommit message (Collapse)AuthorLines
2020-03-09Fix null synthetic_implementors errorGuillaume Gomez-14/+16
2020-01-22Auto merge of #68192 - GuillaumeGomez:remove-inlined-types, r=kinnisonbors-25/+50
Remove usage of global variable "inlined_types" r? @pietroalbini
2020-01-21Rollup merge of #68140 - ecstatic-morse:const-trait-bound-opt-out, r=oli-obkMazdak Farrokhzad-0/+1
Implement `?const` opt-out for trait bounds For now, such bounds are treated exactly the same as unprefixed ones in all contexts. [RFC 2632](https://github.com/rust-lang/rfcs/pull/2632) does not specify whether such bounds are forbidden outside of `const` contexts, so they are allowed at the moment. Prior to this PR, the constness of a trait bound/impl was stored in `TraitRef`. Now, the constness of an `impl` is stored in `ast::ItemKind::Impl` and the constness of a bound in `ast::TraitBoundModifer`. Additionally, constness of trait bounds is now stored in an additional field of `ty::Predicate::Trait`, and the combination of the constness of the item along with any `TraitBoundModifier` determines the constness of the bound in accordance with the RFC. Encoding the constness of impls at the `ty` level is left for a later PR. After a discussion in \#wg-grammar on Discord, it was decided that the grammar should not encode the mutual exclusivity of trait bound modifiers. The grammar for trait bound modifiers remains `[?const] [?]`. To encode this, I add a dummy variant to `ast::TraitBoundModifier` that is used when the syntax `?const ?` appears. This variant causes an error in AST validation and disappears during HIR lowering. cc #67794 r? @oli-obk
2020-01-20rustdoc: Correct order of `async` and `unsafe` in `async unsafe fn`sOliver Middleton-5/+5
2020-01-20Remove usage of global variable "inlined_types"Guillaume Gomez-25/+50
2020-01-20Add `MaybeConst` variant to `{ast,hir}::TraitBoundModifier`Dylan MacKenzie-0/+1
2020-01-20Rollup merge of #68326 - ollie27:rustdoc_hightlight_fatal_errors, ↵Dylan DPC-2/+3
r=GuillaumeGomez rustdoc: Catch fatal errors when syntax highlighting For some errors the lexer will unwind so we need to handle that in addition to handling `token::Unknown`. Fixes #56885 r? @GuillaumeGomez
2020-01-18Rollup merge of #68224 - GuillaumeGomez:prevent-urls-in-headings, r=ollie27Mazdak Farrokhzad-2/+5
Prevent urls in headings Fixes #68215. cc @pietroalbini @ollie27 r? @kinnison
2020-01-17Rollup merge of #68093 - GuillaumeGomez:fix-deref-impl-typedef, r=oli-obkTyler Mandry-14/+20
Fix deref impl typedef Fixes #35295. r? @kinnison
2020-01-17rustdoc: Catch fatal errors when syntax highlightingOliver Middleton-2/+3
For some errors the lexer will unwind so we need to handle that in addition to handling `token::Unknown`.
2020-01-16Rollup merge of #68263 - ollie27:rustdoc_invalid_syntax_highlight_escape, ↵Dylan DPC-1/+1
r=GuillaumeGomez rustdoc: HTML escape codeblocks which fail syntax highlighting r? @GuillaumeGomez
2020-01-16Don't keep link title either, text is generated outside of the link tagGuillaume Gomez-2/+1
2020-01-15rustdoc: HTML escape codeblocks which fail syntax highlightingOliver Middleton-1/+1
2020-01-15Fix rendering on sidebar and update testsGuillaume Gomez-4/+4
2020-01-15Simplify deref impls for type aliasesGuillaume Gomez-37/+26
2020-01-15Include type alias implementationsGuillaume Gomez-21/+32
2020-01-15remove unneeded code from cache.rsGuillaume Gomez-14/+6
2020-01-15formattingGuillaume Gomez-28/+23
2020-01-15Fix deref impl on type aliasGuillaume Gomez-24/+43
2020-01-14Prevent urls in headingsGuillaume Gomez-2/+6
2020-01-14Rollup merge of #68166 - ollie27:rustdoc_help_escape, r=GuillaumeGomezYuki Okushi-2/+2
rustdoc: HTML escape arrows on help popup r? @GuillaumeGomez
2020-01-13Rollup merge of #67959 - liigo:patch-13, r=GuillaumeGomezYuki Okushi-4/+8
rustdoc: improve stability mark arrows ### current ![old-stability-arrow](https://user-images.githubusercontent.com/346530/71863520-134d8b00-3138-11ea-86f9-a98068b3cff9.png) ### new ![new-stability-arrow](https://user-images.githubusercontent.com/346530/71863539-1b0d2f80-3138-11ea-843e-d79b9e5d9eec.png) ### new dark ![dark-stability-arrow](https://user-images.githubusercontent.com/346530/71863563-26f8f180-3138-11ea-9514-050e2c779f90.png)
2020-01-12rustdoc: HTML escape arrows on help popupOliver Middleton-2/+2
2020-01-10nix syntax::errors & prefer rustc_errors over errorsMazdak Farrokhzad-3/+2
2020-01-09rustdoc: use another stability mark arrow, no rotate.Liigo Zhuang-3/+2
2020-01-09rustdoc: improve stability mark arrowsLiigo Zhuang-4/+9
2020-01-07Rollup merge of #67908 - ollie27:rustdoc_const_html_escape, r=GuillaumeGomezYuki Okushi-5/+16
rustdoc: HTML escape const values r? @GuillaumeGomez
2020-01-06Auto merge of #67886 - Centril:rustc_hir_canon_imports, r=nagisabors-5/+6
Nix `rustc_hir` reexports in rustc::hir r? @Zoxc cc @Mark-Simulacrum
2020-01-05rustdoc: HTML escape const valuesOliver Middleton-5/+16
2020-01-05Use `as_deref()` to replace `as_ref().map(...)`Ivan Tham-3/+3
Suggested by @lzutao
2020-01-05Remove rustc_hir reexports in rustc::hir.Mazdak Farrokhzad-5/+6
2020-01-04canonicalize FxHash{Map,Set} importsMazdak Farrokhzad-2/+2
2020-01-02Normalize `syntax::edition` imports.Mazdak Farrokhzad-5/+5
2020-01-02Normalize `syntax::symbol` imports.Mazdak Farrokhzad-3/+3
2020-01-02Normalize `syntax::source_map` imports.Mazdak Farrokhzad-4/+4
2020-01-01Rename `syntax_pos` to `rustc_span` in source codeVadim Petrochenkov-3/+3
2019-12-24Deprecate Error::description for realDavid Tolnay-5/+1
`description` has been documented as soft-deprecated since 1.27.0 (17 months ago). There is no longer any reason to call it or implement it. This commit: - adds #[rustc_deprecated(since = "1.41.0")] to Error::description; - moves description (and cause, which is also deprecated) below the source and backtrace methods in the Error trait; - reduces documentation of description and cause to take up much less vertical real estate in rustdocs, while preserving the example that shows how to render errors without needing to call description; - removes the description function of all *currently unstable* Error impls in the standard library; - marks #[allow(deprecated)] the description function of all *stable* Error impls in the standard library; - replaces miscellaneous uses of description in example code and the compiler.
2019-12-24x.py fmt after previous deignoreMark Rousskov-71/+162
2019-12-24Show value for consts in the documentationOhad Ravid-2/+24
2019-12-23Rollup merge of #67527 - GuillaumeGomez:results-show-too-much, r=kinnisonMazdak Farrokhzad-46/+45
Results show too much Fixes #67461. To reproduce the current issue: search anything, then once the results appears, press escape. They should disappear then re-appear right away. This is because blurring an element triggers the "change" event. r? @kinnison
2019-12-22Format the worldMark Rousskov-2018/+2425
2019-12-22Fix invalid results showing backGuillaume Gomez-0/+4
2019-12-22Improve code readabilityGuillaume Gomez-43/+37
2019-12-22Improve JS code a bit by avoid erasing all event handlersGuillaume Gomez-4/+5
2019-12-22Implement PrintWithSpace trait on hir::MutabilityGuillaume Gomez-12/+12
2019-12-21Remove clean::Mutability enumGuillaume Gomez-2/+2
2019-12-16Rollup merge of #67336 - GuillaumeGomez:fix-js-error, r=Dylan-DPCMazdak Farrokhzad-1/+1
Fix JS error when loading page with search For example when you load this page: https://doc.rust-lang.org/nightly/std/num/struct.NonZeroI8.html?search=foo, you get a nice JS error: ``` TypeError: ev is undefined ``` r? @kinnison
2019-12-15Fix JS error when loading page with searchGuillaume Gomez-1/+1
2019-12-12replace serialize with serde in rustdocAndy Russell-68/+121
2019-12-08Sort auto trait and blanket implementations displayGuillaume Gomez-6/+28
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-08 00:07:18 +0000