That is actually quite dangerous, since it disrega...

# arrow

[simon.vergauwen]

That is actually quite dangerous, since it disregards caching policies, etc. So it would really be a half-baked caching strategy that would probably result in many short-coming pretty quickly.

I like this Kotlin wrapper for Caffeine though. https://github.com/sksamuel/aedile

[streetsofboston]

Memoization works only for pure functions, correct?
If so, caching would work, since the returned result would always be the same...
And if the function is not pure, memoization couldnt be used.

[simon.vergauwen]

Yes, exactly.

[dave08]

I see what you mean...thanks!