rust/compiler/rustc_trait_selection/src/lib.rs, branch 1.56.1https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.56.12021-07-20T14:14:42+00:00Refactor vtable format.2021-07-20T14:14:42+00:00Charles Lewcrlf0710@gmail.com2021-06-17T04:20:18+00:00urn:sha1:d2dc4276fdb5d5c4d8d7ff6906213db6c6ed4d7eremove cfg(bootstrap)2021-05-24T15:07:48+00:00Pietro Albinipietro@pietroalbini.org2021-05-06T11:36:07+00:00urn:sha1:9e22b844ddf503adba315aac4d05909bd947dafehave on_completion record subcycles2021-05-13T09:58:21+00:00Niko Matsakisniko@alum.mit.edu2021-05-11T09:40:42+00:00urn:sha1:89c58eac6826bf6067d4a1cb9d74b9b9282d4688
Rework `on_completion` method so that it removes all
provisional cache entries that are "below" a completed
node (while leaving those entries that are not below
the node).
This corrects an imprecise result that could in turn lead
to an incremental compilation failure. Under the old
scheme, if you had:
* A depends on...
* B depends on A
* C depends on...
* D depends on C
* T: 'static
then the provisional results for A, B, C, and D would all
be entangled. Thus, if A was `EvaluatedToOkModuloRegions`
(because of that final condition), then the result for C and
D would also be demoted to "ok modulo regions".
In reality, though, the result for C depends only on C and itself,
and is not dependent on regions. If we happen to evaluate the
cycle starting from C, we would never reach A, and hence the
result would be "ok".
Under the new scheme, the provisional results for C and D
are moved to the permanent cache immediately and are not affected
by the result of A.
Use iter::zip in compiler/2021-03-26T16:32:31+00:00Josh Stonejistone@redhat.com2021-03-08T23:32:41+00:00urn:sha1:72ebebe474aae7203a27fdc1296617edd01321f1stabilize or_patterns2021-03-20T00:45:32+00:00markmarkm@cs.wisc.edu2020-11-21T21:12:05+00:00urn:sha1:db5629adcba565a674732e829ce6c4a214160835Change x64 size checks to not apply to x32.2021-03-06T16:02:48+00:00Harald van Dijkharald@gigawatt.nl2021-03-06T16:02:48+00:00urn:sha1:95e096d6237298f523e5566be87684d208f7d128
Rust contains various size checks conditional on target_arch = "x86_64",
but these checks were never intended to apply to
x86_64-unknown-linux-gnux32. Add target_pointer_width = "64" to the
conditions.
Stabilize by-value `[T; N]` iterator `core::array::IntoIter`2020-12-29T08:16:46+00:00Simon Sapinsimon.sapin@exyr.org2020-12-29T08:16:46+00:00urn:sha1:61c49d4042af6d392784925cc53afdc830740cd4
Tracking issue: https://github.com/rust-lang/rust/issues/65798
This is unblocked now that `min_const_generics` has been stabilized
in https://github.com/rust-lang/rust/pull/79135.
This PR does *not* include the corresponding `IntoIterator` impl,
which is https://github.com/rust-lang/rust/pull/65819.
Instead, an iterator can be constructed through the `new` method.
`new` would become unnecessary when `IntoIterator` is implemented
and might be deprecated then, although it will stay stable.
TypeVisitor: use `ControlFlow` in rustc_{infer,lint,trait_selection}2020-10-30T11:27:34+00:00LeSeulArtichautleseulartichaut@gmail.com2020-10-21T12:24:35+00:00urn:sha1:4fe735b3209388788176606e10b0bfe953008862Replace some once(x).chain(once(y)) with [x, y] IntoIter2020-10-03T23:51:43+00:00Scott McMurrayscottmcm@users.noreply.github.com2020-10-03T23:51:43+00:00urn:sha1:d74b8e0505b83c72761987c48f3aa3fbb2656573
Now that we have by-value array iterators...
Rollup merge of #77121 - duckymirror:html-root-url, r=jyn5142020-09-25T00:29:45+00:00Jonas Schievinkjonasschievink@gmail.com2020-09-25T00:29:45+00:00urn:sha1:6f3da3d53ff29e604a26d9c94a14147094575b1d
Updated html_root_url for compiler crates
Closes #77103
r? @jyn514