Universal Function Attribute Inference

Richard (Rikki) Andrew Cattermole richard at cattermole.co.nz
Mon Mar 18 10:30:28 UTC 2024


On 18/03/2024 12:12 PM, Timon Gehr wrote:
> On 3/9/24 22:47, Richard (Rikki) Andrew Cattermole wrote:
>> On 10/03/2024 10:26 AM, ryuukk_ wrote:
>>> If there is a significant build penalty, than i hope it's opt-in, i 
>>> personally do not use any of the attributes
>>
>> It shouldn't be significant.
>>
>> It is a minor cost as things go, no reason to start thinking opt-in at 
>> this stage.
> 
> Really? This proposal requires full semantic analysis of any imported 
> function. It is only minor in certain build setups. (E.g., when the 
> project is compiled in a single invocation.)

I am assuming that you generate .di files every time and use that for 
importing, not the .d files.

These days I'm leaning quite heavily towards projects using .di files 
for intermediary steps, due to distribution reasons with shared libraries.

It's already impossible to keep bindings to D code up to date manually, 
I tried pure was a killer on that idea.


More information about the dip.ideas mailing list