Wojciech Nawrocki

> Does this help with your use case? My guess is that it probably doesn't, since you mentioned that you're pretty-printing terms to put in these boxes, so I'm guessing...

> If you're not already using it, please feel free to give it a try! I already was :) It is very cool. > Would love to see your early...

@Montx feel free to ask on IRC/Matrix about anything you might need.

~The curve system from #740 and #530 should address this.~

It seems that there is no GitHub issue on general gameplay replays. It's indeed important to store local graphical input besides the world state in curves if we want to...

Here is a list of things to be done for the new renderer implementation: - [x] Abstraction of render backend - [x] OpenGL 3.3 or higher - [x] Use 4.x...

> Transactions would be a nice feature, but they're a really tough problem and might be best to tackle in a separate crate. The problem with providing transaction support in...

Sorry, I should've been more specific. What I meant is that there is no way to implement __that particular__ transaction implementation ([link again](https://dl.acm.org/citation.cfm?id=2935780)) on top of an existing structure. The...

> with closures I think it'll need very clear explanation to ensure people understand that they risk massive memory blowups if the closure fails to complete quickly. > clones might...

So @stjepang made me aware of some issues I hadn't considered. Firstly, my proposal is only for a certain type of map - hash map. The other type of map...