https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=master 2021-01-30T23:20:24+00:00 2021-01-30T23:20:24+00:00 kadmin julianknodt@gmail.com 2021-01-26T22:49:30+00:00 urn:sha1:6946534d84161353b56157f65f8cdcdfb93df749 2020-12-20T14:15:29+00:00 Ralf Jung post@ralfj.de 2020-11-28T16:32:48+00:00 urn:sha1:7f3e18cc2b24214e10df5434972f4f7cd461fa98 2020-12-20T14:15:28+00:00 Ralf Jung post@ralfj.de 2020-11-21T17:05:29+00:00 urn:sha1:f8d4883dbebf71348abe1134c6f26d48a36256b9 2020-09-02T19:26:37+00:00 Dan Aloni alonid@gmail.com 2020-09-02T07:40:56+00:00 urn:sha1:07e7823c01be1733df2480de19fbbe6b8e9384cf If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2019-11-22T19:01:31+00:00 Dylan MacKenzie ecstaticmorse@gmail.com 2019-11-22T18:45:49+00:00 urn:sha1:fcf4bee7d3d69356a9eb702f9e0a9ddba238d33f The previous test was incorrect. `const fn`s are *always* promotable when inside a `const`, so it should pass. The error was caused by a bug in `promote_consts`. I've added a failing test outside a `const` alongside the existing one, which is now run-pass. 2019-07-07T19:23:31+00:00 David Wood david@davidtw.co 2019-06-13T16:30:49+00:00 urn:sha1:4b1bc2ded91915e232c38cc503b5f110556cf719 2019-07-07T19:23:28+00:00 David Wood david@davidtw.co 2019-06-12T07:46:56+00:00 urn:sha1:a655438988c5f7d100a5423752b7ae0287d582fd 2019-07-07T18:51:31+00:00 David Wood david@davidtw.co 2019-06-12T07:26:16+00:00 urn:sha1:813c994a754b963660b2030699ee1b77c5886ed5 This commit replaces the new error that was being emitted in NLL type check with a call to `report_selection_error` so that the same trait error as before this PR is emitted. 2019-07-07T18:51:29+00:00 David Wood david@davidtw.co 2019-06-12T06:56:07+00:00 urn:sha1:3cca4ceed833493b7ce18c825f14ddd927920e10 This commit adds a `const_in_array_repeat_expressions` feature gate and only create `Candidate::Repeat` if it is enabled. 2019-07-07T18:51:09+00:00 David Wood david@davidtw.co 2019-05-26T11:57:00+00:00 urn:sha1:485a80255b13840551e08f34a268528bbb2a33d9 This commit implements RFC 2203, allowing constants in array repeat expressions. Firstly, the check that the array repeat expression implements `Copy` is removed and re-implemented in `rustc_mir::borrow_check::nll::type_check` by emitting an error when the MIR contains a `Operand::Move` and the type does not implement `Copy`. Next, the `qualify_consts` pass is modified to construct a `Candidate::Repeat` when it would be correct to promote a array repeat expression. Finally, the `promote_consts` pass is modified to promote the candidates previously identified.