Re: newCTFE Status April 2018

[Guillaume Piolat via Digitalmars-d]

On Thursday, 12 April 2018 at 19:40:56 UTC, H. S. Teoh wrote:
On Thu, Apr 12, 2018 at 06:59:33PM +, Stefan Koch via 
Digitalmars-d wrote: [...]


Good to hear work on newCTFE is still ongoing.  Still can't 
wait for it to come to fruition.  Keep up the good work!



T


+1 very curious how much we will be able to parse at compile-time!

Re: newCTFE Status April 2018

[H. S. Teoh via Digitalmars-d]

On Thu, Apr 12, 2018 at 06:59:33PM +, Stefan Koch via Digitalmars-d wrote:
[...]

Good to hear work on newCTFE is still ongoing.  Still can't wait for it
to come to fruition.  Keep up the good work!


T

-- 
You have to expect the unexpected. -- RL

Re: newCTFE Status April 2018

[Stefan Koch via Digitalmars-d]

On Sunday, 8 April 2018 at 09:44:04 UTC, Stefan Koch wrote:

[ ... ]


And again I find a case which we did not handle for years.
When we directly interpret a function which takes a reference to 
a static immutable global as parameter.


This global will be full of zeros since newCTFE had no function 
body to sneak the initialization code into.


This is a close relative of the problem that we have when using 
functionCalls in the global scope interpretations.


Which I solved via a hack that introduces an invisible wrapping 
function to do the calls for the arguments in.


However I do remember there being corner-cases which this 
approach could not solve.

It's time I look for a proper solution.

Cheers,
Stefan