You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflowsC-cleanupCategory: PRs that clean code up or issues documenting cleanup.
Many methods in Scheduler either assert!(self.in_task_context()) or assert!(!self.in_task_context()). This would be more elegantly expressed as a phantom type, Scheduler<TaskCtxt>, Scheduler<SchedCtxt>.
The text was updated successfully, but these errors were encountered:
This un-reverts the reverts of the rusti commits made awhile back. These were reverted for an LLVM failure in rustpkg. I believe that this is not a problem with these commits, but rather that rustc is being used in parallel for rustpkg tests (in-process). This is not working yet (almost! see #7011), so I serialized all the tests to run one after another.
@brson, I'm mainly just guessing as to the cause of the LLVM failures in rustpkg tests. I'm confident that running tests in parallel is more likely to be the problem than those commits I made.
Additionally, this fixes two recently reported issues with rusti.
Fix `redundant_clone` fp
fixes: rust-lang#5973fixes: rust-lang#5595fixes: rust-lang#6998
changelog: Fix `redundant_clone` fp where the cloned value is modified while the clone is in use.
A-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflowsC-cleanupCategory: PRs that clean code up or issues documenting cleanup.
Many methods in Scheduler either
assert!(self.in_task_context())
orassert!(!self.in_task_context())
. This would be more elegantly expressed as a phantom type,Scheduler<TaskCtxt>
,Scheduler<SchedCtxt>
.The text was updated successfully, but these errors were encountered: