Niko Matsakis c14a3d47ea remove memo from PanicGuard ... `PanicGuard` used to own the memo so that, in the case of panic, we could reinstall the old value -- but there's no reason for us to do that. It's just as good to clear the slot in that case and recompute it later. Also, it makes the code nicer to remove it, since it allows us to have more precision about where we know the memo is not null. My motivation though is to work towards "partial cycle recovery". We need a clean and easy way to cancel the ongoing execution and reset the slot to "not computed" (turns out we used that in `maybe_changed_since` too!).		2021-11-10 21:01:00 -05:00
..
incremental	use RefCell::take	2021-10-31 04:13:42 -04:00
parallel	throw Cycle value directly	2021-11-02 12:45:42 -04:00
storage_varieties	remove the DB parameter	2020-07-04 14:17:11 +00:00
cycles.rs	unwind from "block on" for panic/cancellation	2021-11-08 08:07:45 -05:00
dyn_trait.rs	implement the Storage<DB> change	2020-07-04 14:17:10 +00:00
interned.rs	CI runs Clippy	2021-06-17 15:21:51 +01:00
lru.rs	remove the DB parameter	2020-07-04 14:17:11 +00:00
macros.rs	CI runs Clippy	2021-06-17 15:21:51 +01:00
no_send_sync.rs	fix clippy warnings	2021-11-01 13:42:03 -04:00
on_demand_inputs.rs	make "maybe changed since" share code with read	2021-10-30 11:45:12 -04:00
panic_safely.rs	remove memo from PanicGuard	2021-11-10 21:01:00 -05:00
transparent.rs	remove the DB parameter	2020-07-04 14:17:11 +00:00
variadic.rs	remove the DB parameter	2020-07-04 14:17:11 +00:00