Piotr Tarsa

Hi Viktor, I have thought a few hours about promise linking and that complicated mechanism looks unnecessary for me. I've managed to fix the memory leak problem with a simple...

> It's not very interesting to use npm packets or modules on server side along with Java, because there are a lot more libraries for JVM rather than for Nodejs,...

> Please correct me if I'm wrong, but to me, it sounds like "hey, normal assembly doesn't support GC out of the box, so it's more designed to run languages...

> What do you mean by arbitrary memory management here? WASM allows you to manage memory on a very low level. For example, if you compile Rust to WASM you...

allocating extra buffers and catching OOME when sorting primitives is rather unsatisfactory. you're not giving a reliable option for sorting under low memory conditions. IMO at least the single-threaded primitives...

Hi Guillaume, I think I have another solution :) Instead of shrinking dictionary size you can use flags to denote which dictionary entries are valid and which are possibly dirty....

> Hey Piotr ^^ Thanks, yes this is looking like a promising idea at first impression. I'll have to investigate and benchmark it but it would clearly greatly reduce the...

> I don't really think unless I missed your point that this would be an issue. Instead of pre-building one big dictionary you could just as well pre-build a small...

In reality it has an object (i.e. the kernel accesses an object). I've created following simple test program: ```scala package boxed class Logic { def run(): Unit = { var...

@gzm0 Could you defer detecting the cycles to the point where linking error occurs? If there is a linkage error in method X then detect whether method X is in...