Hisham Muhammad
Hisham Muhammad
That does sound like a good idea!...
If anyone is willing to try their hand at a PR, I'd rather have the syntax originally suggested by @Saecki , I think it'd be more consistent with the existing...
Yes, `record` instances do not set metatables implicitly. The `record` keyword is a type constructor and not a type itself. Interesting thought: try making _type another generic type argument (`function`)....
> So if records are not a real data type, but rather just a keyword, I suggest to clarify that in the tutorial. From what I've read there I expected...
> Maybe I'm asking something stupid but the project has no chat-room/community place so couldn't ask before writing here. It's a very valid question! For now this works as a...
This is a "lenient" behavior we're currently letting slip because `x = and ` is a very common Lua idiom, which means that the resulting value will be either of...
Yes, in technical terms we say that the type checker is unsound. But this is by design, so in this case it is not broken. This does not mean that...
There are observable behavior differences (e.g, `select("#", f() )`) between a Lua function that returns explicit nil with `return nil` (return arity 1) versus with `return` (return arity 0). In...
@Kepler-Br This is not exactly the same, because generics in an _expression_ context would ambiguous with the `
@euclidianAce that it good feedback. This model indeed does not cover multiple-level inheritance well and shouldn't be seen as a "clunky way of doing OOP". I think for OOP we...