CTFE Status

Dominikus Dittes Scherkl via Digitalmars-d digitalmars-d at puremagic.com
Mon Dec 5 02:26:39 PST 2016


On Monday, 5 December 2016 at 08:07:11 UTC, ketmar wrote:
> On Monday, 5 December 2016 at 07:55:32 UTC, deadalnix wrote:
>> On Monday, 5 December 2016 at 04:26:35 UTC, Stefan Koch wrote:
>>> I just improved the handling of void initializations.
>>> Now the code is less pessimistic and will allow them if they 
>>> are assigned to before use.
>>> However using void variables at ctfe will not result in any 
>>> performance wins.
>>
>> Void initialization are allowed at CTFE ?
>
> not now, but it looks like needless limitation. any void 
> initialization can be converted to "fill the things with 
> zeroes" in CTFE engine.

On the contrary. If something is NOT initialized, it uses its 
default (e.g. zeroes), but if it is =void it should be an error 
to use it before any assignment.



More information about the Digitalmars-d mailing list