summary refs log tree commit diff
path: root/src/librustc_error_codes
AgeCommit message (Collapse)AuthorLines
2020-06-02Rollup merge of #72880 - GuillaumeGomez:cleanup-e0637, r=Dylan-DPCYuki Okushi-1/+4
Clean up E0637 explanation r? @Dylan-DPC
2020-06-01Clean up E0637 explanationGuillaume Gomez-1/+4
2020-06-01Rollup merge of #72818 - GuillaumeGomez:cleanup-e0622, r=Dylan-DPCDylan DPC-3/+11
Clean up E0622 explanation r? @Dylan-DPC
2020-05-31Clean up E0622 explanationGuillaume Gomez-3/+11
2020-05-30Rollup merge of #72540 - davidtwco:issue-67552-mono-collector-comparison, ↵Ralf Jung-1/+1
r=varkor mir: adjust conditional in recursion limit check Fixes #67552. This PR adjusts the condition used in the recursion limit check of the monomorphization collector, from `>` to `>=`. In #67552, the test case had infinite indirect recursion, repeating a handful of functions (from the perspective of the monomorphization collector): `rec` -> `identity` -> `Iterator::count` -> `Iterator::fold` -> `Iterator::next` -> `rec`. During this process, `resolve_associated_item` was invoked for `Iterator::fold` (during the construction of an `Instance`), and ICE'd due to substitutions needing inference. However, previous iterations of this recursion would have called this function for `Iterator::fold` - and did! - and succeeded in doing so (trivially checkable from debug logging, `()` is present where `_` is in the substs of the failing execution). The expected outcome of this test case would be a recursion limit error (which is present when the `identity` fn indirection is removed), and the recursion depth of `rec` is increasing (other functions finish collecting their neighbours and thus have their recursion depths reset). When the ICE occurs, the recursion depth of `rec` is 256 (which matches the recursion limit), which suggests perhaps that a different part of the compiler is using a `>=` comparison and returning a different result on this recursion rather than what it returned in every previous recursion, thus stopping the monomorphization collector from reporting an error on the next recursion, where `recursion_depth_of_rec > 256` would have been true. With grep and some educated guesses, we can determine that the recursion limit check at line 818 in `src/librustc_trait_selection/traits/project.rs` is the other check that is using a different comparison. Modifying either comparison to be `>` or `>=` respectively will fix the error, but changing the monomorphization collector produces the nicer error.
2020-05-29Rollup merge of #72731 - GuillaumeGomez:cleanup-e0619, r=Dylan-DPCDylan DPC-0/+1
Add missing empty line in E0619 explanation r? @Dylan-DPC
2020-05-29Add missing empty line in E0619 explanationGuillaume Gomez-0/+1
2020-05-29Rollup merge of #72495 - GuillaumeGomez:cleanup-e0601, r=Dylan-DPCYuki Okushi-2/+3
Improve E0601 explanation r? @Dylan-DPC
2020-05-29Rollup merge of #72605 - GuillaumeGomez:cleanup-e0617, r=Dylan-DPCDylan DPC-0/+11
Add working example for E0617 explanation r? @Dylan-DPC
2020-05-28standardize limit comparisons with `Limit` typeDavid Wood-1/+1
This commit introduces a `Limit` type which is used to ensure that all comparisons against limits within the compiler are consistent (which can result in ICEs if they aren't). Signed-off-by: David Wood <david@davidtw.co>
2020-05-27Add working example for E0617 explanationGuillaume Gomez-0/+11
2020-05-25Rollup merge of #72567 - GuillaumeGomez:cleanup-e0608, r=Dylan-DPCDylan DPC-1/+1
Clean up E0608 explanation r? @Dylan-DPC
2020-05-25Clean up E0608 explanationGuillaume Gomez-1/+1
2020-05-24Rollup merge of #72530 - GuillaumeGomez:cleanup-e0602, r=Dylan-DPCRalf Jung-2/+2
Clean up E0602 explanation r? @Dylan-DPC
2020-05-24Clean up E0602 explanationGuillaume Gomez-2/+2
2020-05-23Improve E0601 explanationGuillaume Gomez-2/+3
2020-05-22Rollup merge of #72461 - GuillaumeGomez:cleanup-e0600, r=Dylan-DPCDylan DPC-1/+1
Clean up E0600 explanation r? @Dylan-DPC
2020-05-22Rollup merge of #72375 - GuillaumeGomez:cleanup-e0599, r=Dylan-DPCDylan DPC-0/+15
Improve E0599 explanation r? @Dylan-DPC
2020-05-22Rollup merge of #72345 - GuillaumeGomez:cleanup-e0593, r=Dylan-DPCRalf Jung-0/+11
Clean up E0593 explanation r? @Dylan-DPC
2020-05-22Rollup merge of #72235 - GuillaumeGomez:cleanup-E0590, r=Dylan-DPCRalf Jung-3/+7
Clean up E0590 explanation r? @Dylan-DPC
2020-05-22Clean up E0590 explanationGuillaume Gomez-3/+7
2020-05-22Clean up E0600 explanationGuillaume Gomez-1/+1
2020-05-20Improve E0599 explanationGuillaume Gomez-0/+15
2020-05-20Implement `#[ffi_const]` and `#[ffi_pure]` function attributesMatthias Schiffer-0/+3
Introduce function attribute corresponding to the `const`/`pure` attributes supported by GCC, clang and other compilers. Based on the work of gnzlbg <gonzalobg88@gmail.com>.
2020-05-19Clean up E0593 explanationGuillaume Gomez-0/+11
2020-05-18Add documentation for asm!Amanieu d'Antras-10/+10
2020-05-17Rollup merge of #72259 - crlf0710:ascii_only_check, r=petrochenkovRalf Jung-0/+34
Disallow forbidden usage of non-ascii identifiers. Part of RFC2457, this tightens allowed identifiers back to ascii only in two situations. r? @petrochenkov
2020-05-17Disallow forbidden usage of non-ascii identifiers.Charles Lew-0/+34
2020-05-16Fix typo Arbintrary to ArbitraryRustin-Liu-1/+1
Signed-off-by: Rustin-Liu <rustin.liu@gmail.com>
2020-05-14Rollup merge of #72191 - GuillaumeGomez:cleanup-e0589, r=Dylan-DPCDylan DPC-0/+2
Clean up E0589 explanation r? @Dylan-DPC
2020-05-14Rollup merge of #72127 - jademcgough:long-error-explanation-E0228, ↵Dylan DPC-1/+41
r=petrochenkov add long error explanation for E0228 Add long explanation for the E0228 error code Part of #61137 Let me know if this is wrong at all (or can be written more clearly), I'm still learning Rust.
2020-05-14Clean up E0589 explanationGuillaume Gomez-0/+2
2020-05-14Rollup merge of #72169 - GuillaumeGomez:cleanup-e0582, r=Dylan-DPCRalf Jung-2/+2
Clean up E0582 explanation r? @Dylan-DPC
2020-05-14Rollup merge of #72137 - GuillaumeGomez:cleanup-e0581, r=Dylan-DPCRalf Jung-3/+6
Clean up E0581 explanation r? @Dylan-DPC
2020-05-13Clean up E0582 explanationGuillaume Gomez-2/+2
2020-05-12add long error explanation for E0228Jade McGough-1/+41
2020-05-12Clean up E0581 explanationGuillaume Gomez-3/+6
2020-05-11Rollup merge of #72107 - GuillaumeGomez:cleanup-e0579, r=Dylan-DPCDylan DPC-4/+6
Clean up E0579 explanation r? @Dylan-DPC
2020-05-11Rollup merge of #72077 - GuillaumeGomez:cleanup-E0571, r=Dylan-DPCDylan DPC-3/+3
Improve E0571 wording r? @Dylan-DPC
2020-05-11Clean up E0579 explanationGuillaume Gomez-4/+6
2020-05-10Improve E0571 wordingGuillaume Gomez-3/+3
2020-05-09Add missing backtick in E0569 explanationGuillaume Gomez-1/+1
2020-05-03Add stability attribute to E0539 error examplesunexge-0/+2
2020-05-02Add `#![feature(staged_api)]` attribute to E0539 error examplesunexge-0/+4
2020-05-02Add long error explanation for E0539unexge-1/+43
2020-04-24Rollup merge of #71426 - contrun:fix-e0751-explanation, r=estebankDylan DPC-1/+1
fix error code in E0751.md reference: https://github.com/rust-lang/rust/issues/71304
2020-04-23Rollup merge of #71461 - GuillaumeGomez:improve-e0567, r=Dylan-DPCDylan DPC-4/+2
Improve E0567 explanation r? @Dylan-DPC
2020-04-23Rollup merge of #71396 - DeeDeeG:improve-e0308-again, r=estebankDylan DPC-5/+4
Improve E0308 error message wording again Hello again, I recently did this PR: #70242 I felt the error message could be further improved, so I made [a post on the Rust community forum](https://users.rust-lang.org/t/looking-for-feedback-on-an-improved-error-message-for-e0308/40004) to ask for feedback. (Also, there were some comments on my original PR that I took into consideration as well.) This PR is my attempt to take all the feedback into account and propose a better and simplified error message that should still be accurate. Its main benefit is having simpler grammar, and hopefully being easier to read and understand. Thanks to everyone who commented and gave feedback, and thank you for taking a look at this PR.
2020-04-23Improve E0567 explanationGuillaume Gomez-4/+2
2020-04-23fix error code for E0751YI-1/+1