Qingtian

I think that's expected. To collect a series-frame, the algorithm's run time is: ~~O(MxN)~~ ~~M: number of series-buffers in each series-frame~~ ~~N: number of node-frames~~ The node-frames will not be...

@dockimbel Sorry, `N` is number of `series-frame`. `O(MxN)` is not correct. It's linear to the number of series-buffers. So it should be `O(n)`, which `n` is the number of series-buffers....

@hiiamboris We'll definitely need a better GC. This is a [Simple GC](https://www.red-lang.org/2018/12/064-simple-gc-and-pure-red-gui-console.html). It's even no mechanism to recycle external resources (image!, face!, port!, etc.) I think it fulfills its purpose...

@dockimbel Ok. I did miss the `free-node` calling in `compact-series-frame` and `compact-series-frame`. It iterates over all the `node-frame` each time a node is freed. So the execution time of those...

1. `event/key` is wrong in `on-key-down`, but it's correct in `on-key`, right? The title of the issue is not accurate. 2. For `on-key-down` and `on-key-up`, the value of `event/key` should...

> Currently, it's not the same. Why should it be? I think only event/picked (scancode) has to be the same. To make it easier to know which key is pressed...

@hiiamboris OK. So you mark it by using `series/flags`. You can remove the comment for `img-node!`.

@hiiamboris This one: https://github.com/red/red/blob/50d58d68c1fe1c264bca7f8a4189fc99942efc0b/runtime/platform/image-wic.reds#L53

@hiiamboris Nope. The same as the other platforms, no GC support for image was implemented.

`get/any` works as expected. ``` >> c: context [f: does [print 123]] get/any 'c/f == func [][print 123] ``` In the interpreter, the get value will be evaluated if no...