Hisham Muhammad

I've kept it private so far because the internal format changes every now and then (it's already different in the `next` branch, and I have further uncommitted changes in the...

@bjornbm tests and documentation are still pretty much missing, because I wanted to iterate as quickly as possible to experiment with the usability of these features... but once the dust...

@euclidianAce @catwell Thanks a lot for the feedback!! And, yeah, I totally get that sentiment — over the years I've accepted that my work on FOSS projects happens in bursts....

Also, speaking of writeups, it's funny that CI is failing because the `tl.type_check` function is exceeding the maximum number of upvalues per function in Lua 5.1. Looks like old Lua...

Update: it took me a big reorganization in [d885f90](https://github.com/teal-language/tl/pull/732/commits/d885f90a0a88d21713c9f2b1b3d838a850ac6599) to get CI green. This is because the size of tl.tl started hitting size limits in both Lua 5.1 (number of...

Regarding "making the type system more nominal", here's one interesting example: https://toot.kottman.xyz/@michal/111860362351389256 > One thing I'm missing (or haven't yet found in docs) is "distinct type" (borrowing term from Nim)...

@catwell thanks for the test case! I haven't really worked on the relationship between generics and interfaces/`where` yet, so that's a good starting point. > Is that expected or do...

@Feuermurmel No immediate plans to change this, but it's not entirely off the table either. There's a long thread debating on this topic over at the Discussions tab, on which...

Teal does bidirectional type inference to try to avoid the need for this. In your example above, doing `local foo: integer = get_foo()` should make the expected type flow into...

> There might be some cases where this workaround isn't sufficient but I can't find it at the moment. I honestly don't see it as a workaround, since it amounts...