Li Jin

It's a good idea. Since interfaces are like some kinds of type info, we might need to implement the static typed system to support these features and get the work...

Yes, there is a syntax sugar for mixing. You can use it with ```moonscript class A using B, C ``` and get ```lua local A -- 1 do -- 1...

1. It's intended behavior for existential op. Expression ends with a `?` will be compiled to `(expr ~= nil)`. Maybe we can add existential check syntax to the with statement...

Improvements 1, 7 were done by commit d80160356d7b7119d164ada51867cecb0a371f09

How about a little modification for the syntax to make it look more consist? ```Moonscript a = close: true, close#: => print "out of scope" b = add#: (left, right)->...

The new syntax is now implemented in the commit 1df786307c1983b8ce693e3916081a8bcd4e95ae with some extra usages as: ```moonscript a = close: true, close#: => print "out of scope" b = add#: (left,...

Yes, it causes conflict. If an expression followed by # symbol means getting its meta table. Codes `a.add#` will be compiled to `getmetatable(a.add)` instead of `getmetatable(a).__add`. So using `a.add.#` can...

I like the idea of `['close']#: => print "out of scope"` and got it implemented. And I understand the `#.`, `#\` can be used as a new operator. But to...

With a little more thought, I feel the first syntax won't be a better choice because there will be 4 rules to memorize for using the metatable syntax and each...

I like this syntax improvement and got it implemented. Hybrid cases are solved with parser error which makes things simpler. ```moonscript mt = a.# #:mt = a a = #:mt...