Promise rejections not cleared immediately from cache about memoizee HOT 2 OPEN

@lukashavrlant thanks for report.

In this given case, it's because memoizee did not manage to reset the cache before this second invocation is issued (note that it's issued immediately after first resolved).

e.g. if you add one tick gap after first invocation resolves but before next one is made, you'd see expected result:

	await memoized(3)
		.then((x) => console.log(`result: ${x}`))
		.catch((e) => console.error(e.message));
	await new Promise((resolve) => process.nextTick(resolve));
	await memoized(3)
		.then((x) => console.log(`result: ${x}`))
		.catch((e) => console.error(e.message));

Delay in deleting the cache can be attributed to fact that memoizee internally attempts to escape the promise chain (to avoid errors swallowing effect), and that puts promise result processing one tick further.

This design will be questioned when working on v1, so it might be that in v1 it'll be improved, and you'll see cache being cleared on time. For that reason I'll keep this issue open.

from memoizee.

@medikoo OK, thank you for the explanation 🙂

from memoizee.