about summary refs log tree commit diff
path: root/src
AgeCommit message (Collapse)AuthorLines
2019-04-18Use -mergefunc-use-aliases for any LLVM >= 8Josh Stone-1/+1
2019-04-18Auto merge of #60046 - euclio:missing-error-code-descriptions, r=estebankbors-936/+563
hide `--explain` hint if error has no extended info Fixes #59848. r? @estebank
2019-04-18Auto merge of #58702 - taiki-e:libcore-2018, r=Centrilbors-332/+342
libcore => 2018 Transitions `libcore` to Rust 2018; cc #58099 r? @Centril
2019-04-18Update testsvarkor-19/+19
2019-04-18hide `--explain` hint if error has no extended infoAndy Russell-936/+563
2019-04-18Update miriTim Diekmann-14/+14
2019-04-18Implement event filtering for self-profiler.Michael Woerister-28/+97
2019-04-18Auto merge of #60025 - JohnTitor:rename-files, r=petrochenkovbors-2519/+2519
Rename files about error codes fixes #60017 This PR will be failed in tidy. <details> <summary>The log is here:</summary> ``` tidy check tidy error: duplicate error code: 411 tidy error: Documents\GitHub\rust\src\librustc_resolve\diagnostics.rs:83: __diagnostic_used!(E0411); tidy error: Documents\GitHub\rust\src\librustc_resolve\diagnostics.rs:84: err.code(DiagnosticId::Error("E0411".to_owned())); tidy error: duplicate error code: 424 tidy error: Documents\GitHub\rust\src\librustc_resolve\diagnostics.rs:90: debug!("smart_resolve_path_fragment: E0424, source={:?}", source); tidy error: Documents\GitHub\rust\src\librustc_resolve\diagnostics.rs:92: __diagnostic_used!(E0424); tidy error: Documents\GitHub\rust\src\librustc_resolve\diagnostics.rs:93: err.code(DiagnosticId::Error("E0424".to_owned())); some tidy checks failed ``` </details> I'd like to fix this but I don't know what to do. I will work on later. Please let me know if you have any solutions. r? @petrochenkov
2019-04-18Use new `needs-(profiler|sanitizer)-support` compiletest directive to clean ↵Michael Woerister-30/+20
up some run-make tests.
2019-04-18Fix small errors in docs for `rchunks_exact` and `rchunks_exact_mut`.Nathan Kleyn-3/+3
The documentation for `rchunks_exact` said it started at the beginning of the slice, bit it actually starts at the end of the slice. In addition, there were a couple of "of the slice of the slice" duplicate phrases going on for `rchunks_exact` and `rchunks_exact_mut`. This fixes #60068.
2019-04-18Add codegen test that makes sure PGO instrumentation is emitted as expected.Michael Woerister-0/+20
2019-04-18compiletest: Allow for tests requiring profiler-rt or sanitizer-rt support.Michael Woerister-0/+21
2019-04-18Prefix PROFILER_SUPPORT and SANITIZER_SUPPORT test env vars with RUSTC_ to ↵Michael Woerister-16/+16
make things clearer.
2019-04-18Update run-make PGO test to new commandline syntax.Michael Woerister-1/+1
2019-04-18Use more realistic example for thread builderAleksey Kladov-1/+1
Stack size of 10 **bytes** does not make any sense: the minimal possible stack size is greater anyway.
2019-04-18Auto merge of #60071 - RalfJung:miri, r=oli-obkbors-14/+14
update miri Fixes https://github.com/rust-lang/rust/issues/60040
2019-04-18make liballoc internal test suite mostly pass in MiriRalf Jung-1/+15
2019-04-18update miriRalf Jung-14/+14
2019-04-18Auto merge of #60058 - varkor:const-generics-ty-refactor, r=cramertjbors-38/+47
Make const parameters enforce no variance constraints Fixes https://github.com/rust-lang/rust/issues/60047. Also includes some minor const refactoring for convenience.
2019-04-18Auto merge of #60048 - estebank:issue-54954, r=sanxiynbors-0/+48
Fix ICE on const evaluation of const method Fix #54954.
2019-04-18Update stdsimdTaiki Endo-0/+0
2019-04-18libcore => 2018Taiki Endo-332/+342
2019-04-18Simplify the returning of a Result a bitJan Nils Ferner-2/+1
2019-04-18Auto merge of #60051 - estebank:fn-sugg, r=davidtwcobors-19/+16
Do not mention missing `PartialOrd` impl when involving uncalled fns
2019-04-17Give custom error for E0277 on `?` error caseEsteban Küber-6/+18
2019-04-17Point at try `?` on errors affecting the err match arm of the desugared codeEsteban Küber-13/+21
2019-04-18Make PlaceProjectionsIter a proper iteratorSantiago Pastorino-4/+18
2019-04-17whitelist rtm x86 cpu featuretyler-1/+5
2019-04-17review comment: add extra docEsteban Küber-1/+3
2019-04-18Add a test for unused const parametersvarkor-0/+14
2019-04-18Const parameters should impose no variance constraintsvarkor-29/+16
2019-04-18Add a FIXME to collectorvarkor-0/+2
2019-04-18Add own_requires_monomorphizationvarkor-9/+15
2019-04-18Update rustfmt to 1.2.1topecongiro-5/+5
2019-04-18Rollup merge of #60037 - eddyb:actually-its-param, r=estebankMazdak Farrokhzad-20/+20
Resolve inconsistency in error messages between "parameter" and "variable". The inconsistency was introduced in 104fe1c4db24f860b890dfd25577f23ee111279a (#33619), when a label saying `type variable` was added to an error with a message talking about `type parameters`. Given that `parameter` is far more prevalent when referring to generics in the context of Rust, IMO it should be that in both the message and the label. r? @nikomatsakis or @estebank
2019-04-18Rollup merge of #60036 - rust-lang:nrc-patch-1, r=XanewokMazdak Farrokhzad-2/+2
Remove nrc from toolstate pings 🙉
2019-04-18Rollup merge of #59984 - gluyas:collections-with_capacity-doc-fix, r=rkruppeMazdak Farrokhzad-4/+3
Remove collection-specific `with_capacity` documentation from `std::collections` Fixes #59931 The style of `std::collections` module doc is very much a beginner friendly guide, and documenting niche, collection-specific behaviour feels out of place, if not brittle. The note about `VecDeque` is outdated (see issue), and while `Vec` probably won't change its guarantees any time soon, the users who are interested in its allocation properties will find that in its own documentation.
2019-04-18Rollup merge of #59908 - lzutao:str_escape, r=SimonSapinMazdak Farrokhzad-0/+2
Re-export core::str::{EscapeDebug, EscapeDefault, EscapeUnicode} in std cc #59893
2019-04-17Correct E0392 diagnosticvarkor-5/+8
2019-04-17Do not mention missing `PartialOrd` impl when involving uncalled fnsEsteban Küber-19/+14
2019-04-18Rename moduleYuki OKUSHI-1/+1
2019-04-18Remove unnecessary conditionYuki OKUSHI-1/+1
2019-04-18Rename diagnositc_list into error_codesYuki OKUSHI-0/+0
2019-04-18Rename files in docYuki OKUSHI-11/+11
2019-04-17Auto merge of #59527 - matklad:sized-index, r=Centrilbors-0/+23
Add test checking that Index<T: ?Sized> works I've noticed that we have an `Idx: ?Sized` bound on the **index** in the `Index`, which seems strange given that we accept index by value. My guess is that it was meant to be removed in https://github.com/rust-lang/rust/pull/23601, but was overlooked. If I remove this bound, `./x.py src/libstd/ src/libcore/` passes, which means at least that this is not covered by test. I think there's three things we can do here: * run crater with the bound removed to check if there are any regressions, and merge this, to be consistent with other operator traits * run crater, get regressions, write a test for this with a note that "hey, we tried to fix it, its unfixable" * decide, in the light of by-value DSTs, that this is a feature rather than a bug, and add a test cc @rust-lang/libs EDIT: the forth alternative is that there exist a genuine reason why this is the case, but I failed to see it :D
2019-04-17Fix ICE on const evaluation of const methodEsteban Küber-0/+48
2019-04-18making adjust_span a closureSaleem Jaffer-22/+22
2019-04-17Make iterate take a FnOnce with PlaceBase and PlaceProjectionIterSantiago Pastorino-214/+236
2019-04-17Place::iterate do not take an accumulator anymore, hide that in a private fnSantiago Pastorino-3/+10
2019-04-17Place::unroll -> Place::iterateSantiago Pastorino-6/+6
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-27 18:07:51 +0000