Hisham Muhammad

This should be fixed in 0.14. I'm going to close this; feel free to reopen if the problem reappears!

This is a big question! > I think it's a good idea (although Lua purists might not like it?) I tend to lean towards "good idea" but I also realize...

> I was looking at the docs, does this work, and what does it compile to: To this: ```lua local Point = {} function Point:move(dx: number, dy: number) self.x =...

> A simple encoding is to use the "class" as the metatable for the instances, and have __index be a circular link: This is sort of what users do by...

> OOP in lua is so ad hoc and dynamic that I think this would easily feel restrictive to some people. I would never prevent people to manipulate metatables explicitly...

> Trying to make the compiler understand and type simple metatable patterns for OO was also something we tried with Typed Lua Ah, I did not mean that. The compiler...

@euclidianAce This is a really interesting experiment! This is really another step towards intersection types (as were function overloads in records and array-records). I'm starting to wonder if the compiler...

This is an interesting feature request! From the get-go, I had decided to not do super-smart inference (which lead to complicated compilers and hard-to-decipher error messages) and one of my...

No immediate plans to add this since we don't even have subtyping in type variables (yet), but let's see ahead! But it's interesting that TypeScript added this restricted form of...

Yes, this PR does not change the other subtyping rules, only the arity rules, so yes, you can pass an explicit nil. In fact, this PR is implemented in pieces,...