Juraj Kirchheim

Yeah, in Haxe this will probably be super awkward. What might be interesting is the ability to generate json schema, although that will also hit a wall when it comes...

What's the problem with [json-schema-to-typescript](https://www.npmjs.com/package/json-schema-to-typescript)?

Ok, this is really weird but I cannot really track down the cause of it. I've tried commenting out everything in `TypeTools` to find out that even such harmless functions...

Yeah, sorry, I'll try to make a minimal example for Simn. But in any case it's nothing I think I can solve, so you'll have to not use tink_macro or...

Well, the way it's "supposed to work" is more like: ```haxe enum Buffer { @:json({ target: 34963 }) ElementArrayBuffer(elementArrayBuffer:{ buffer:Int, byteOffset:Int, byteLength:Int }); @:json({ target: 34962 }) ArrayBuffer(arrayBuffer:{ buffer:Int, byteOffset:Int,...

Well, could solve that with abstracts or static extensions, but without really knowing the use case I can hardly give qualified advise ^^ That said, I will look into making...

Hard to know for sure without more context, but yes, it's a possible cause.

> I'd first like to check if the the b part of hxb really has an unacceptable overhead in reality. Yes, yes. This is primarily of a backup plan ;)...

I agree with Simn: Property access shouldn't be O(N), because that's misleading to the reader.

Is there some good design we could steal? It would also be nice if one could formulate such contracts for the underlying value of an abstract (e.g. not NaN).