https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.61.0 2022-03-30T05:39:38+00:00 2022-03-30T05:39:38+00:00 Yuri Astrakhan YuriAstrakhan@gmail.com 2022-03-30T05:39:38+00:00 urn:sha1:7e8201ae0a57ef63b876cf2bf9ae388426f1dda5 This PR attempts to clean up some minor spelling mistakes in comments 2022-03-28T05:25:32+00:00 Michael Goulet michael@errs.io 2022-03-10T00:11:28+00:00 urn:sha1:928388bad20572e9ffa575319bb6d3b636bcdc69 2022-03-20T19:36:26+00:00 Camille GILLOT gillot.camille@gmail.com 2022-03-20T19:02:18+00:00 urn:sha1:0b49d05ea33d68391e3d5472f3398d0ad1d9f9a6 2022-03-20T19:36:08+00:00 Camille GILLOT gillot.camille@gmail.com 2022-03-20T17:26:09+00:00 urn:sha1:056951d6289e3fbba444cbadec8b4eea7f92928e Taking a Diagnostic by move would break the usual pattern `diag.label(..).emit()`. 2022-03-16T15:35:24+00:00 mark markm@cs.wisc.edu 2022-01-23T00:49:12+00:00 urn:sha1:bb8d4307eb723850e98bcb52d71d860a4aba220a There are a few places were we have to construct it, though, and a few places that are more invasive to change. To do this, we create a constructor with a long obvious name. 2022-03-14T16:24:58+00:00 Matthias Krüger matthias.krueger@famsik.de 2022-03-14T16:24:58+00:00 urn:sha1:6548a368c8c66c802ba710dd9fede228dc65587e Improve `expect` impl and handle `#[expect(unfulfilled_lint_expectations)]` (RFC 2383) This PR updates unstable `ExpectationIds` in stashed diagnostics and adds some asserts to ensure that the stored expectations are really empty in the end. Additionally, it handles the `#[expect(unfulfilled_lint_expectations)]` case. According to the [Errors and lints docs](https://rustc-dev-guide.rust-lang.org/diagnostics.html#diagnostic-levels) the `error` level should only be used _"when the compiler detects a problem that makes it unable to compile the program"_. As this isn't the case with `#[expect(unfulfilled_lint_expectations)]` I decided to only create a warning. To avoid adding a new lint only for this case, I simply emit a `unfulfilled_lint_expectations` diagnostic with an additional note. --- r? `@wesleywiser` I'm requesting a review from you since you reviewed the previous PR https://github.com/rust-lang/rust/pull/87835. You are welcome to reassign it if you're busy :upside_down_face: rfc: [RFC-2383](https://rust-lang.github.io/rfcs/2383-lint-reasons.html) tracking issue: https://github.com/rust-lang/rust/issues/85549 cc: `@flip1995` In case you're also interested in this :) 2022-03-10T15:23:40+00:00 T-O-R-U-S bageliq@protonmail.com 2022-02-12T19:16:17+00:00 urn:sha1:72a25d05bf1a4b155d74139ef700ff93af6d8e22 This updates the standard library's documentation to use the new syntax. The documentation is worthwhile to update as it should be more idiomatic (particularly for features like this, which are nice for users to get acquainted with). The general codebase is likely more hassle than benefit to update: it'll hurt git blame, and generally updates can be done by folks updating the code if (and when) that makes things more readable with the new format. A few places in the compiler and library code are updated (mostly just due to already having been done when this commit was first authored). 2022-03-09T23:51:10+00:00 Esteban Kuber esteban@kuber.com.ar 2022-03-09T22:47:00+00:00 urn:sha1:ac2afa033443cd697e92b17e5a5263bd9640d9d0 Fix #94192. 2022-03-07T18:59:10+00:00 xFrednet xFrednet@gmail.com 2022-03-06T13:18:28+00:00 urn:sha1:d39d60971bafe34f626585e4887e7eec726fe972 2022-03-07T17:54:17+00:00 Michael Howell michael@notriddle.com 2022-03-07T17:50:47+00:00 urn:sha1:fbd4cfa0f8272a5c74d6c5ed882032a08d5b8d09 Fixes #94646