On Friday, 11 August 2017 at 09:27:47 UTC, Stefan Koch wrote:
> On Tuesday, 1 August 2017 at 21:27:32 UTC, Stefan Koch wrote:
>> [ ... ]
>
> Hey guys,
>
> I just finished &&.
Hooray!
So what's still missing? Or is this now complete enough to release?

On Friday, 11 August 2017 at 20:13:04 UTC, Dominikus Dittes Scherkl wrote:
> On Friday, 11 August 2017 at 09:27:47 UTC, Stefan Koch wrote:
>> On Tuesday, 1 August 2017 at 21:27:32 UTC, Stefan Koch wrote:
>>> [ ... ]
>>
>> Hey guys,
>>
>> I just finished &&.
> Hooray!
> So what's still missing? Or is this now complete enough to release?

it's almost at the point where I am okay with making a newCTFE-1.0 release.
it will correctly coexist with the old engine such that the things it currently cannot do are still taken care of by the old engine.

Things left to do :

- Deal with more void initialization correctly.
- Unions
- Classes
- Exceptions
- some complex types such as int[][3][]
- string-decoding foreach. like: (foreach(dchar utf32; uft8someString))
- associative arrays (though we may change druntime to a ctfe-able version, which would also allow having aa-literals computed at ctfe usable at runtime)

There are a few corner-cases in the supported feature set where it will fallback to the old interpreter but fixing those is a matter of hand-work not head-work (as they _should_ not impact the design):)

On Tuesday, 1 August 2017 at 21:27:32 UTC, Stefan Koch wrote:
> [ ... ]

Hi Guys,

I've fixed a few ABI bugs and as a result my alternative to std.bitmanip.bitfields complies now.
I've also made an intrinsic for the concat operation.
Which causes ~= to be 6-10x faster when it's heavily used.

The huge space requirements for heavy ~= are not yet solved though.
To pass the unittests regardless which does ~= 4096 times on a moderately long string;
I've had to bump the ctfe heapSpace.
Therefore newCTFE will allocate 1GB at startup which causes it to die on 32bit targets.
This issue will be worked when _most_ of the ABI is finalized (i.e. when classes and unions are in)

On Tuesday, 1 August 2017 at 21:27:32 UTC, Stefan Koch wrote:
> [ ... ]

Hi there,

I've just adjusted the memory allocation behavior.
newCTFE will now start-out allocating 32M of memory at startup.
and increase the allocated space in 8x steps if it hits the limit while executing concat code.
In which case of course it needs to copy 32meg in the worst-case.
Therefore you will feel a noticeable slowdown if are using ~= and happen to just go slightly over the limit.
But if you overstep the limit by much the increased speed of concat will compensate for the hit.

The new behavior enables us to compile on 32bit targets again.

On Tuesday, 1 August 2017 at 21:27:32 UTC, Stefan Koch wrote:
> [ ... ]

Guys,

newCTFE is green on 64 and 32bit!

I've finally fixed || and &&.
For good!

whooooohooooo ;)

Release is coming closer!

On Monday, 14 August 2017 at 11:25:14 UTC, Stefan Koch wrote:
>
> Guys,
>
> newCTFE is green on 64 and 32bit!
>
> I've finally fixed || and &&.
> For good!
>
> whooooohooooo ;)
>
> Release is coming closer!

Cool.

On Monday, 14 August 2017 at 11:25:14 UTC, Stefan Koch wrote:
> On Tuesday, 1 August 2017 at 21:27:32 UTC, Stefan Koch wrote:
>> [ ... ]
>
> Guys,
>
> newCTFE is green on 64 and 32bit!
>
> I've finally fixed || and &&.
> For good!
>
> whooooohooooo ;)
>
> Release is coming closer!

There are times I wish the D forum had upvote buttons. This is one of those times.

--
  Biotronic

On Monday, 14 August 2017 at 11:25:14 UTC, Stefan Koch wrote:
> On Tuesday, 1 August 2017 at 21:27:32 UTC, Stefan Koch wrote:
>> [ ... ]
>
> Guys,
>
> newCTFE is green on 64 and 32bit!
>
> I've finally fixed || and &&.
> For good!
>
> whooooohooooo ;)
>
> Release is coming closer!

Wow, I can't wait!

On Mon, Aug 14, 2017 at 01:54:26PM +0000, Per Nordlöw via Digitalmars-d wrote:
> On Monday, 14 August 2017 at 11:25:14 UTC, Stefan Koch wrote:
> > On Tuesday, 1 August 2017 at 21:27:32 UTC, Stefan Koch wrote:
> > > [ ... ]
> > 
> > Guys,
> > 
> > newCTFE is green on 64 and 32bit!
> > 
> > I've finally fixed || and &&.
> > For good!
> > 
> > whooooohooooo ;)
> > 
> > Release is coming closer!
> 
> Wow, I can't wait!

+1, me too!


T

-- 
Famous last words: I *think* this will work...

On Monday, 14 August 2017 at 11:25:14 UTC, Stefan Koch wrote:
> Release is coming closer!

Nice, keep up the good work.