named arguments, string interpolation, please stop.

[Timon Gehr]

On 1/11/24 22:45, Jonathan M Davis wrote:
> On Thursday, January 11, 2024 12:33:48 PM MST Walter Bright via Digitalmars-d
> wrote:
>> On 1/11/2024 5:07 AM, deadalnix wrote:
>>> These are just simple thing that I have on top of my mind, but there are a
>>> ton more.
>>
>> Thanks for taking the time to write this list. I would like to see all of
>> your issues, though! Let's make a list and then have a bugzilla entry for
>> each of them, so we can start picking them off.
>>
>>   > such as @nogc, has been a productivity disaster
>>
>> I don't really understand this. Just don't use @nogc?
> 
> ...
> I'm increasingly inclined to think that most attributes are primarily of
> theoretical benefit

No, theory predicts many of those issues with the way attributes are 
designed in D currently. x)

> ... Trying to use as many attributes as possibly (which many D developers
> think is best practice) really does seem to be like you're putting concrete
> on your code, making refactoring far, far harder than it would be in most
> languages - or if you'd just minimize the attributes that you're using.
> ...

Yes. Unfortunately it seems to be very hard to make new D developers 
understand this point until they run into the problem themself.

You put an attribute if the code is wrong if it does not conform to the 
attribute, otherwise you should not put it. But in D, often both choices 
are incorrect if you want to interact with code that does have 
attributes applied to it.