- 05 1月, 2020 11 次提交
-
-
由 Andy Russell 提交于
-
由 bors 提交于
Rollup of 4 pull requests Successful merges: - #67137 (libstd uses `core::panic::Location` where possible.) - #67709 (Introduce an option for disabling deduplication of diagnostics) - #67775 (Make "use $crate" a hard error) - #67812 (Tweak and extend internal BTreeMap documentation, including debug asserts.) Failed merges: r? @ghost
-
由 Dylan DPC 提交于
Tweak and extend internal BTreeMap documentation, including debug asserts. Gathered from work on various other pull requests (e.g. #67725, #67686).
-
由 Dylan DPC 提交于
Make "use $crate" a hard error Closes #37390
-
由 Dylan DPC 提交于
Introduce an option for disabling deduplication of diagnostics With the intent of using it in UI tests (https://github.com/rust-lang/rust/pull/67122). The option is boolean (`-Z deduplicate-diagnostics=yes/no`) and can be specified multiple times with later values overriding earlier values (`-Z deduplicate-diagnostics=no -Z deduplicate-diagnostics=yes` == `-Z deduplicate-diagnostics=yes`), so it can be set in a hierarchical way, e.g. UI testing infra may disable the deduplication by default with specific tests being able to enable it back.
-
由 Adam Perry 提交于
-
由 Adam Perry 提交于
-
由 Adam Perry 提交于
-
由 Adam Perry 提交于
* Removes unnecessary feature flag from track_caller test. * Tests of panic internals no longer need to explicitly construct Location. * Add #![warn(const_err)] to retain-never-const per @oli-obk. * Add track_caller test with diverging function.
-
由 Adam Perry 提交于
-
- 04 1月, 2020 26 次提交
-
-
由 Stein Somers 提交于
Co-Authored-By: NRobin Kruppe <robin.kruppe@gmail.com>
-
由 Guillaume Gomez 提交于
Remove unused `#[link_name = "m"]` attributes These were perhaps supposed to be `#[link(name = "m")]` but linking libm should be handled by the libc crate anyway. They should have triggered a compile error: #47725
-
由 Guillaume Gomez 提交于
Clean up err codes r? @Dylan-DPC
-
由 Guillaume Gomez 提交于
improve some `Drop`-related error messages
-
由 Guillaume Gomez 提交于
Revert `const_err` lint checking of casts Reverts part of #67676 r? @oli-obk cc @SimonSapin
-
由 bors 提交于
Move early and late lint mechanisms to librustc_lint. As requested, split from #67737 r? @Zoxc
-
由 Yuki Okushi 提交于
-
由 bors 提交于
Rollup of 8 pull requests Successful merges: - #66913 (Suggest calling method when first argument is `self`) - #67531 (no longer promote non-pattern const functions) - #67773 (Add a test for #37333) - #67786 (Nix reexports from `rustc_span` in `syntax`) - #67789 (Cleanup linkchecker whitelist) - #67810 (Implement uncommon_codepoints lint.) - #67835 (tweak wording of mismatched delimiter errors) - #67845 (Also remove const-hack for abs) Failed merges: r? @ghost
-
由 Dylan DPC 提交于
-
由 Mazdak Farrokhzad 提交于
Also remove const-hack for abs Closes #67842. r? @oli-obk
-
由 Mazdak Farrokhzad 提交于
tweak wording of mismatched delimiter errors This PR improves the wording of the "incorrect delimiter" error messages. Here's a quick rationale: - *"un-closed" -> "unclosed"*: "unclosed" is valid English, so there's no need to hyphenate the prefix. This should be pretty uncontroversial, I think. - *"close delimiter" -> "closing delimiter"*: In my anecdotal experience, I've always heard "closing delimiter" or "closing parenthesis". In addition, the codebase already uses this terminology in comments and function names more than "close delimiter", which could indicate that it's more intuitive. - "incorrect delimiter" -> "mismatched delimiter": "Incorrect delimiter" is vague; why is it incorrect? "mismatched" clearly indicates why the delimiter is causing the error. r? @estebank
-
由 Mazdak Farrokhzad 提交于
Implement uncommon_codepoints lint. Part of #55467 . The checks of `$crate` and `{{root}}` are very unfortunate. But i'm not sure where they belongs to.
-
由 Mazdak Farrokhzad 提交于
Cleanup linkchecker whitelist linkchecker is no longer run on the compiler docs so they can be removed from the whitelist.
-
由 Mazdak Farrokhzad 提交于
Nix reexports from `rustc_span` in `syntax` Remove reexports `syntax::{source_map, symbol, edition}` and use `rustc_span` paths directly. r? @petrochenkov
-
由 Mazdak Farrokhzad 提交于
Add a test for #37333 The test checks that we reuse the CGU of a crate when the implementation details of an `extern crate` have changed. Signed-off-by: NMichal Terepeta <michal.terepeta@gmail.com>
-
由 Mazdak Farrokhzad 提交于
no longer promote non-pattern const functions This is trying to pack-pedal a bit on promotion feature creep, as proposed by @EddyB [here](https://github.com/rust-lang/const-eval/issues/19#issuecomment-472799062): possibly, a sane subset of `const fn` that we could promote are those that are just constructors -- the same subset that we might want to allow in pattern position at some point. So, this removes the `rustc_promotable` attribute from the three functions they identified that do not fit this pattern. The first step is to run crater to see if there is code in the wild that relies on this being promotable. r? @oli-obk
-
由 Mazdak Farrokhzad 提交于
Suggest calling method when first argument is `self` Closes: #66782 I've explored different approaches for this MR but I think the most straightforward is the best one. I've tried to find out if the methods for given type exist (to maybe have a better suggestion), but we don't collect them anywhere and collecting them is quite problematic. Moreover, collecting all the methods would require rewriting big part of the code and also could potentially include performance degradation, which I don't think is necessary for this simple case.
-
由 Oliver Middleton 提交于
These were perhaps supposed to be `#[link(name = "m")]` but linking libm should be handled by the libc crate anyway.
-
由 Guillaume Gomez 提交于
-
由 Guillaume Gomez 提交于
-
由 Andy Russell 提交于
-
由 Andy Russell 提交于
- Use the span of the predicate - Use the def's description instead of "struct/enum" (notably incorrect for unions) - Align formatting with other error messages
-
由 jumbatm 提交于
-
由 bors 提交于
Attempt to fix intermittent failures of pgo-branch-weights test. This PR tries to fix the intermittent failures of the pgo-branch-weights test (https://github.com/rust-lang/rust/issues/67746). The failing instances show no `!prof` annotations in LLVM IR. One possible cause is that the instrumented binary did not record anything. This is something I've occasionally seen happen for similarly small programs when using GNU ld as linker. The linker would not properly append the instruction counter sections, leading to most counters being dropped. This PR makes the test use the Gold linker instead. It also makes each command exit immediately on failure so we can pinpoint the failure source better, should there still be a problem. r? @Mark-Simulacrum
-
由 bors 提交于
update miri Fixes https://github.com/rust-lang/rust/issues/67793
-
- 03 1月, 2020 3 次提交
-
-
由 mental 提交于
Co-Authored-By: NYuki Okushi <huyuumi.dev@gmail.com>
-
由 Vadim Petrochenkov 提交于
-
由 Vadim Petrochenkov 提交于
-