Alexander Klingenbeck

The verbosity is managable if you use type inference where you can. Functions like `twgl.createTextures` will especially benefit from typescript, as you get full intellisense and type checking for all...

@colorpump : I'm still working on this. Twgl is a huge library, if you use all the sub modules. [Here's a incomplete version, if you don't need the submodules](https://gist.github.com/mode777/4f8eb25b123b2c5627034f797834f949)

@colorpump Not sure if I understand your question, but consuming the submodules will work just like in javascript: ``` import * as twgl from "twgl.js"; const info = twgl.primitives.create3DFBufferInfo(gl); ```...

@colorpump This seems like a reasonable way to go. Ideally you would run `npm install twgl.js`, then `import * from 'twgl.js'` and get intellisense straight away. I think this should...

@paulushub I agree but the currently released version of type2docfx on npm already seems to target the yet unreleased docfx v3. The "proper" solution should be unlisting on npm...

I did some digging in the script and it seems like blender calls the image "TLM_Overlay.png.001" instead of "TLM_Overlay.png" . Changing it in the script solves the problem but I...

I think there are valid use cases, where you want a detailed error report without killing the vm. * A test runner that should continue when a test fails *...

@mhermier It returns null for a new Fiber and works correctly on a yielded Fiber. The current implementation will stop walking the stack after the 16kb buffer was filled.

> (sorry for the noise) Maybe a better solution would be to allow to iterate on stack frames entries, and let wren make the string. It is suboptimal, may have...

> Yes but that info can be used in plain text, viewed inside a debugger and displayed in columns in a table, the user can make a stack trace formatter...