Kevin Leung

I worked on a bigint implementation this week. It covers a few but not all targets for now. But I think it can be a foundation for RSA. https://github.com/kevinresol/bigint

> This violates the abstraction because `Some` is not `Option`, it's actually `T -> Option`. Things like this have to be considered in the detailed design. From my understanding, `enum...

> I don't follow where that `T->Status` comes from. ```haxe enum abstract Status(Option) to Option { final Continue = Some; final End = None; } $type(Status.Continue); // T -> Status...

I think this proposal should be renamed as "abstract enum over enum constructors" to avoid confusion. In the following I am trying to think aloud my understanding of the concepts...

> * agree that a well-defined syntax is a good thing > * remove inline markup from Haxe 4, so that when we finally agree that doing better than Notepad...

With semantics (compiler is aware of attributes and Haxe code inside attributes): ```haxe var x = trace("{")}/> ``` vs "minimal assumption": ```haxe var x = trace("\{")}/> ``` or even: ```haxe...

It is all about balance and compromises. You always mentioned the design of the macro system was a "minimal" one. But remember you chose to design it with Haxe semantics....

The issue is that error thrown in javascript causes a native crash (note the pointers to native functions in the original issue), and absent of javascript stack make it very...

I don't think a javascript debugger can debug a hard crash at native level.

and I will just copy the example code in case people fail to follow the link ```js const noble = require("@abandonware/noble"); class Scanner { constructor() { noble.on("scanStart", this.onScanStart.bind(this)); noble.on("stateChange", ()...