klesun
commented
6 years ago Apparently (paste here your laugh) iterators are disposable. This conflicts with the MultiType class which has methods like hasNumericKeys, getIdeaType, getKeyNames, etc... and they all have to iterate through the types. And after we iterate once, the second time we get an exception.
I believe the MultiType itself should be eliminated. Everything should return DeepType iterator and if you need to perform multiple operations (mostly in the entry function), either explicitly put them in an array there, or think of how to reuse them in one iterator (like doing all operations in one foreach). For the time being I guess best would be to put iterator passed to MultiType to an array and slowly remove all usages of MultiType from the project.
I also have this MemoizingIterable, it have bugs though. It does not help memory and probably wastes a lot of time on storing the iterated values, but it should work conceptually same way as normal iterator so that in the entry function we still have iterator over the final results that are not calculated till you run it.
Another problem is that each expression gets cached upon resolution, but iterator can't be cached since it is disposable. An option, I guess, is to use my MemoizingIterable here. This way we are still iterating types one by one and we can (supposedly) reuse this iterator when taking value from cache.
Caused by key assignment in 
Insufficient keys returned from call to a function that does 
klesun-misc
But it does work sometimes though:
Should help with the #43
This should drastically increase performance, but raises some issues. I'll describe them here and list possible solutions.