mattn

Right. Or how about this? This is way to hide freeing code. ``` c int n; char buf[256]; chan_recv_int(c, &n); chan_recv_string(c, buf, sizeof(buf)); ```

Agreed. We will have to add new types for each users want.

I don't look code yet but it seems correct behavior.

Most of users not use module. So we can change specification of module, I think.

On my first design, module meant namespace not class. So I did not expect that module can be instance with new keyword. But most of users does not use module...

Let's add new code for class and make "module" deprecated. Go's reflect does not have APIs to make struct dynamically. So adding class on anko will be useful. Class has...

Yes, few years ago, I worked in progress for struct. But some APIs did not exists in that time. https://github.com/mattn/anko/commit/158d91ccdd07c67e99204497290ec9e687b7a0cd

Anko's defer statement doesn't work like Go's one since anko doesn't have named return parameters for a function. Anko can not re-write return value. Also current implementation doesn't have recover().

```go func foo() { var i = 0 defer println("foo", i) i++ defer println("bar", i) i++ defer println("bar", i) i++ defer println("bar", i) i++ defer println("bar", i) } foo() ```...

This implementation is strange since VM run defer even if it is in if/for block. It must be in func block. ```go var time = import("time") for { defer println("foo")...