Re: Battle-plan for CTFE
On Mon, Oct 24, 2016 at 8:17 AM, Stefam Koch via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote: > On Monday, 24 October 2016 at 05:57:42 UTC, Stefam Koch wrote: > >> On Sunday, 16 October 2016 at 00:27:50 UTC, Uplink_Coder wrote: >> >>> >>> Little update here: >>> The LLVM backend is almost on feature parity. >>> Meaning that that soon the new CTFE engine is a real jit. >>> In the process I discoverd quite a few horrible bugs and inconsistency >>> in the API. >>> I am quite astonished that it ever ran before :) >>> >> >> Hey Guys, >> >> I am still dealing with the many bugs that have surfaced. >> It is really crazy how something so broken could have worked that well. >> > So true of computer programming. Particularly if the documentation for the API is awol. > >> Originally I planned adding a ton of features, but that can only happen >> If the fundamental issues are fixed. >> > > However at the D Meetup in Berlin, I have gotten some positive feedback > concerning my ByteCode-Layer. > Once the bugs are fixed and the edges are smoothed over I can see finding > it's way into other parts of the compiler. > > Cool, thanks for the feedback.
Re: Battle-plan for CTFE
On Monday, 24 October 2016 at 05:57:42 UTC, Stefam Koch wrote: On Sunday, 16 October 2016 at 00:27:50 UTC, Uplink_Coder wrote: Little update here: The LLVM backend is almost on feature parity. Meaning that that soon the new CTFE engine is a real jit. In the process I discoverd quite a few horrible bugs and inconsistency in the API. I am quite astonished that it ever ran before :) Hey Guys, I am still dealing with the many bugs that have surfaced. It is really crazy how something so broken could have worked that well. Originally I planned adding a ton of features, but that can only happen If the fundamental issues are fixed. However at the D Meetup in Berlin, I have gotten some positive feedback concerning my ByteCode-Layer. Once the bugs are fixed and the edges are smoothed over I can see finding it's way into other parts of the compiler.
Re: Battle-plan for CTFE
On Sunday, 16 October 2016 at 00:27:50 UTC, Uplink_Coder wrote: Little update here: The LLVM backend is almost on feature parity. Meaning that that soon the new CTFE engine is a real jit. In the process I discoverd quite a few horrible bugs and inconsistency in the API. I am quite astonished that it ever ran before :) Hey Guys, I am still dealing with the many bugs that have surfaced. It is really crazy how something so broken could have worked that well. Originally I planned adding a ton of features, but that can only happen If the fundamental issues are fixed.
