Closed nikolay-egorov closed 2 years ago
Not sure if we really need one more entity for almost the same thing...
I suggest to leave plain realisation of map recreation in Notebook, without caching. Like
val ans = mutableMapOf<String, Result<Any?>>()
ans.putAll(
varsState.mapValues {
it.value.value
}
)
return ans
It's way convinient to keet it here than to assamble this call in bytecode
I changed api, introduced private object for debub purposes in repl
Actually I do worry about
==
performance, maybe it's really ok to recreate each time presentable map anew