Nidin Vinayakan

Nice catch. I will investigate it.

In second example did you mean optional return. In that case following is more declarative since we need either void or a type. ```typescript getContext():void|type ```

```typescript getContext()?: RenderContext ``` If above signature means `getContext` return `RenderContext` or `null` we dont need `?` operator since all types are nullable. ```typescript getContext(): RenderContext { return null; }...

We need to implement default arguments.

Let's move it to V2 since it's not blocking basic functionality On Wed 12. Apr 2017 at 4:21 PM, Wink Saville wrote: > Is this needed for v1, i'd vote...

But user can pass any mixed combination of union types that might break the code. for example. ```typescript let a:int32 = 10; let b:float32 = 1.2356; Foo.add(a, b); //error in...

Good question. Never thought about it. If int is a pointer to utf-8 bytes it make sense.

Hi Tom, Thanks for your reply. No worries about the delay. The issue is rendering order of the red block. I just created it to demonstrate the problem. All objects...

Yes, of course. I am waiting for [WebGPU](https://en.wikipedia.org/wiki/WebGPU) spec to be standardised. Mean while you can check [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). I am contributing to AS. TurboScript will not be a TypeScript to...