summary refs log tree commit diff
path: root/src
AgeCommit message (Collapse)AuthorLines
2020-01-271.41.0 stable releasePietro Albini-1/+1
2020-01-27switch bootstrap compiler to stable 1.40.0Pietro Albini-2/+2
2020-01-27Make pointers to statics internalMatthew Jasper-33/+89
2020-01-23review commentsEsteban Küber-16/+14
2020-01-23Do not ICE on malformed suggestion spansEsteban Küber-5/+28
2020-01-23format librustc_errorsMark Rousskov-404/+421
2020-01-23Distinguish between private items and hidden items in rustdocDavid Tolnay-78/+138
I believe rustdoc should not be conflating private items (visibility lower than `pub`) and hidden items (attribute `doc(hidden)`). This matters now that Cargo is passing --document-private-items by default for bin crates. In bin crates that rely on macros, intentionally hidden implementation details of the macros can overwhelm the actual useful internal API that one would want to document. This PR restores the strip-hidden pass when documenting private items, and introduces a separate unstable --document-hidden-items option to skip the strip-hidden pass. The two options are orthogonal to one another.
2020-01-23format librustdocMark Rousskov-775/+839
2020-01-23Revert parts of #66405.Nicholas Nethercote-111/+80
Because it caused major performance regressions in some cases. That PR had five commits, two of which affected performance, and three of which were refactorings. This change undoes the performance-affecting changes, while keeping the refactorings in place. Fixes #67454.
2020-01-23fmt data data structuresMark Rousskov-68/+51
2020-01-17rustdoc: Don't allow `#![feature(...)]` on stable or betaOliver Middleton-2/+1
(cherry picked from commit 40571995984a0f2c466f77955e7d147887c2179b)
2020-01-17Add ICE regression testsEsteban Küber-0/+34
(cherry picked from commit f6e9fd037a7b55f8f4fe78694b77d9788b18dfeb)
2020-01-17Change `next_point` when `shrink_to_hi` is more appropriateEsteban Küber-17/+13
(cherry picked from commit b93ef68245807bac97cd17ea9eaa13169380d815)
2020-01-17Fix invalid bounding boxEsteban Küber-1/+1
(cherry picked from commit d558f6a570a782cd1c2e54de790f4f968b0de5f1)
2020-01-17Fix `next_point` to be unicode awareEsteban Küber-1/+1
(cherry picked from commit 3250057da983fa4d5bfd0799adaa41cb038f0e25)
2020-01-17Do not ICE on unicode next pointEsteban Küber-1/+24
Use `shrink_to_hi` instead of `next_point` Fix #68000. (cherry picked from commit fcd850fc5db2501d14b2e0cbfac8aa890d700e55)
2020-01-17expect `fn` after `const unsafe` / `const extern`Mazdak Farrokhzad-1/+42
(cherry picked from commit 915db7ae6430baef99f186ba40f08e105b7694fe)
2020-01-13Fix rebase damageJonas Schievink-1/+0
2020-01-13Do not ICE on lifetime error involving closuresEsteban Küber-2/+38
2020-01-13Treat extern statics just like statics in the "const pointer to static" ↵Oliver Scherer-2/+71
representation
2020-01-13Use the correct type for static qualifsMatthew Jasper-8/+22
2020-01-13Reenable static linking of libstdc++ on windows-gnuMateusz Mikuła-1/+1
2020-01-13Don't suppress move errors for union fieldsMatthew Jasper-9/+79
2020-01-13Move command-related tests into command/Jeremy Fitzhardinge-0/+0
2020-01-13Fix up Command Debug output when arg0 is specified.Jeremy Fitzhardinge-2/+30
PR https://github.com/rust-lang/rust/pull/66512 added the ability to set argv[0] on Command. As a side effect, it changed the Debug output to print both the program and argv[0], which in practice results in stuttery output ("echo echo foo"). This PR reverts the behaviour to the the old one, so that the command is only printed once - unless arg0 has been set. In that case it emits "[command] arg0 arg1 ...".
2019-12-17Switch to bootstrapping from dev-static stableMark Rousskov-5/+5
2019-12-16Rollup merge of #67349 - petertodd:2019-unsize-docs, r=CentrilMazdak Farrokhzad-1/+1
Minor: update Unsize docs for dyn syntax
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-16Rollup merge of #67323 - Centril:tes, r=davidtwcoMazdak Farrokhzad-18/+17
make transparent enums more ordinary By recognizing that structs & unions have one variant, we can make the treatment of transparent enums less ad-hoc. cc https://github.com/rust-lang/rust/issues/60405 r? @davidtwco
2019-12-16Rollup merge of #67322 - lzutao:nonzero-use-self, r=joshtriplettMazdak Farrokhzad-3/+3
use Self alias in place of macros
2019-12-16Rollup merge of #67318 - Centril:spdocs, r=matthewjasperMazdak Farrokhzad-17/+63
Improve typeck & lowering docs for slice patterns cc #62254 r? @matthewjasper
2019-12-16Rollup merge of #67308 - dtolnay:fast_rebind, r=alexcrichtonMazdak Farrokhzad-15/+0
Delete flaky test net::tcp::tests::fast_rebind This test is unreliable for at least 3 users on two platforms: see #57509 and #51006. It was added 5 years ago in #22015. Do we know whether this is testing something important that would indicate a bug in our implementation, or if it's fine to remove? r? @sfackler @alexcrichton because this somewhat resembles #59018 Closes #57509. Closes #51006.
2019-12-16Rollup merge of #67249 - ranma42:improve-starts-with-literal-char, r=BurntSushiMazdak Farrokhzad-15/+48
Improve code generated for `starts_with(<literal char>)` This PR includes two minor improvements to the code generated when checking for string prefix/suffix. The first commit simplifies the str/str operation, by taking advantage of the raw UTF-8 representation. The second commit replaces the current str/char matching logic with a char->str encoding and then the previous method. The resulting code should be equivalent in the generic case (one char is being encoded versus one char being decoded), but it becomes easy to optimize in the case of a literal char, which in most cases a developer might expect to be at least as simple as that of a literal string. This PR should fix #41993
2019-12-16Add benchmarks for `start_with` and `ends_with`Andrea Canciani-0/+44
2019-12-16Minor: update Unsize docs for dyn syntaxPeter Todd-1/+1
2019-12-16improve lower_pat_slice docs + while -> forMazdak Farrokhzad-12/+26
2019-12-16Rollup merge of #67325 - Centril:push-fake-read, r=matthewjasperMazdak Farrokhzad-48/+23
cleanup with push_fake_read ...and make things a bit more readable. r? @matthewjasper
2019-12-16Rollup merge of #67324 - Centril:mir-build-match-doc-fix, r=matthewjasperMazdak Farrokhzad-2/+1
Fix repetition in matches/mod.rs r? @matthewjasper
2019-12-16Rollup merge of #67317 - lcnr:type_name_docs, r=jonas-schievinkMazdak Farrokhzad-1/+1
fix type_name_of_val doc comment .
2019-12-16Rollup merge of #66771 - SimonSapin:panic-stability, r=KodrAusMazdak Farrokhzad-8/+10
Stabilize the `core::panic` module `std::panic` is already stable. `core::panic::PanicInfo` and `core::panic::Location` are stable and can be used through that path because of a bug in stability checking: #15702
2019-12-16Rollup merge of #66735 - SOF3:feature/str_strip, r=KodrAusMazdak Farrokhzad-1/+72
Add str::strip_prefix and str::strip_suffix Introduces a counterpart for `Path::strip_prefix` on `str`. This was also discussed in https://internals.rust-lang.org/t/pre-pr-path-strip-prefix-counterpart-in-str/11364/.
2019-12-16Rollup merge of #66570 - lzutao:stabilize-result-map_or, r=Dylan-DPCMazdak Farrokhzad-5/+4
stabilize Result::map_or r? @SimonSapin Closes #66293
2019-12-16Rollup merge of #65778 - bdonlan:stable_weak_count, r=dtolnayMazdak Farrokhzad-49/+35
Stabilize `std::{rc,sync}::Weak::{weak_count, strong_count}` * Original PR: #56696 * Tracking issue: #57977 Closes: #57977 Supporting comments: > Although these were added for testing, it is occasionally useful to have a way to probe optimistically for whether a weak pointer has become dangling, without actually taking the overhead of manipulating atomics. Are there any plans to stabilize this? _Originally posted by @bdonlan in https://github.com/rust-lang/rust/issues/57977#issuecomment-516970921_ > Having this stabilized would help. Currently, the only way to check if a weak pointer has become dangling is to call `upgrade`, which is by far expensive. _Originally posted by @glebpom in https://github.com/rust-lang/rust/issues/57977#issuecomment-526934709_ Not sure if stabilizing these warrants a full RFC, so throwing this out here as a start for now. Note: per CONTRIBUTING.md, I ran the tidy checks, but they seem to be failing on unchanged files (primarily in `src/stdsimd`).
2019-12-15Fix JS error when loading page with searchGuillaume Gomez-1/+1
2019-12-15cleanup with push_fake_readMazdak Farrokhzad-48/+23
2019-12-15Fix repetition in matches/mod.rsMazdak Farrokhzad-2/+1
2019-12-15make transparent enums more ordinaryMazdak Farrokhzad-18/+17
2019-12-15use Self alias in place of macrosLzu Tao-3/+3
2019-12-15improve hir::PatKind::Slice docsMazdak Farrokhzad-2/+9
2019-12-15document check_pat_sliceMazdak Farrokhzad-0/+25
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-03-02 15:55:53 +0000