From a4ef195a9f4c0e018673a872f8f3020cc5337a36 Mon Sep 17 00:00:00 2001 From: Qyriad Date: Thu, 4 Apr 2024 10:46:44 -0600 Subject: always re-eval cached failures This is terrible UX, and frankly an eval failure should be a cache invalidation anyway. This removes the CachedEvalError type entirely. Fixes #223. Change-Id: I91f8003eabd0ea45003024e96d1de3c7ae8e49d8 --- doc/manual/rl-next/no-cache-eval-errors.md | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/manual/rl-next/no-cache-eval-errors.md (limited to 'doc') diff --git a/doc/manual/rl-next/no-cache-eval-errors.md b/doc/manual/rl-next/no-cache-eval-errors.md new file mode 100644 index 000000000..c80d96dba --- /dev/null +++ b/doc/manual/rl-next/no-cache-eval-errors.md @@ -0,0 +1,8 @@ +--- +synopsis: re-evaluate cached evaluation errors +cls: 771 +--- + +"cached failure of [expr]" errors have been removed: expressions already in the +eval cache as a failure will now simply be re-evaluated, removing the need to +set `--no-eval-cache` or similar to see the error. -- cgit v1.2.3