Cached tokio runtime after panic about evcxr HOT 1 CLOSED

I see two potential solutions:

• assume that accessing the runtime via the poisoned lock is ok via into_inner in

  evcxr/evcxr/src/eval_context.rs

  Lines 581 to 590 in 47d5646

  	if self.state.async_mode {
  	user_code = CodeBlock::new()
  	.generated(stringify!(evcxr_variable_store
  	.lazy_arc("evcxr_tokio_runtime", || std::sync::Mutex::new(
  	tokio::runtime::Runtime::new().unwrap()
  	))
  	.lock()
  	.unwrap()))
  	.generated(".block_on(async {")
  	.add_all(user_code);

• Or recreating the runtime. This could work by moving the mutex generation into the lazy_arc method, e.g. one could check if the mutex in the returned arc is poissoned and recreate it in that case.

from evcxr.