sirisian

I updated the README, but at the same time I wonder if this is ideal. Consider how BigInt works. It returns "bigint" and not "object". I think I'd need to...

ah, yeah that makes sense. Sounds good then.

Based on feedback I incorporated unions - which might still have issues with parsing ambiguities. I also added the interface sections because they're important. If TS handles things better for...

I think one of the biggest things to define is member ordering for data. Each derived class would simply be placed after the parent in the inheritance tree. The alignment...

https://github.com/sirisian/ecmascript-types#member-memory-alignment-and-offset Added more details. There's still some details to refine which are listed at the bottom of that section. Might need more examples.

> Are these types basically comments, that the language does not enforce at all, but anyone can build a type checker that's able to read and understand these comments? No....

> What happens if I do user.name = 24? Is an error immediately thrown? Refer to this: https://github.com/sirisian/ecmascript-types/issues/29 I haven't thought about it in a while, but it's definitely a...

I haven't ignored this. Been thinking about it on and off for months. The big idea behind the colon is the hard visual break that I don't believe whitespace gives....

In the extending function interfaces example here: https://github.com/sirisian/ecmascript-types#extending-interfaces the whole example would look like: ```js interface A { (string):void; } interface B extends A { (string, string):void; } function F(a:B)...

Investigate alternative syntax in the decorator proposal. Using overloading: ```js function test(value, context) { } function test(a:string) { return (value, context) => { } } class A { @test @test('test')...