caching function that returns mutable produces confusing behaviour
cmcaine opened this issue · 2 comments
cmcaine commented
Unclear how to fix this nicely - maybe you want your function to return a reference to the same mutable struct each time and you don't mind that the contents of that struct has changed between function calls?
In my case I've just split my function up so I can cache the immutable string I get from a glorified HTTP.get() operation and I parse the string into a Dict later.
Anyway, I think this should maybe be documented?
zgornel commented
Could you provide a minimal example of the issue/bug you are refering to?
zgornel commented
Closing for lack of details.