Perry van Wesel

Seems problem is that if you set strict=true, TS inserts a bunch of undefined types, and if you try to call something that is possibly undefined (should be disallowed by...

try/finally does not behave as expected when rethrowing

6

See `re-throw` test in `test/unit/error.spec.ts`: ```ts const i: number = ${i}; function foo() { try { try { if (i === 0) { throw "z"; } } catch (e) {...

Proposal: Lualib override plugins

2

In the last 2 weeks we received two requests for the ability to modify lualib output with plugins. One for supplying an environment-specific implementation of __TS__New, and another for a...

Unexpected undefined signature declaration in validation of function assignments. Requires some more investigation why signature is undefined, even though the type checker can infer the signature alright. Playground reproduction (check...

Consider the following project: ``` main.ts otherfile.ts ``` And tsconfig.json: ```json { "compilerOptions": { "declaration": true }, "tstl": { "luaBundle": "bundle.lua", "luaBundleEntry": "main.ts" }, } ``` ## Expected output ```...

Move annotations to language extensions where possible

2

Now that we have language extensions, we can move some of the more hacky annotations to language extensions instead. Some of the annotations that can be moved: - `@forRange` -...

We need to test if the SourceMapTraceBack actually works correctly

20

Currently it seems like our tests do not cover this yet.

Misssing context validation cases

1

```ts // function in object so considered method with self const fn = ({ f: () => void }) => f(); // Lambda function without context const g = ()...

As the title says. These features should be removed from the code of the modules in the bundle, and added to the top-level bundle code.

Currently for values such as luaLibImport, not specifying them will lead whichever code is checking the option to encode what the default value is. We should find a way to...