On Sunday, 6 February 2022 at 13:40:00 UTC, Paolo Invernizzi wrote:
> On Sunday, 6 February 2022 at 13:33:53 UTC, Paul Backus wrote:
>>
>> @mustUse is a user-defined attribute, and the official style guide says that names of UDAs should be camelCased:
>>
>> https://dlang.org/dstyle.html#naming_udas
>
> ... This matches conventions of the built in attributes like @safe,  __@nogc__  ...

Presumably this is referring to the part about the first letter being lower-case, since the built-in attributes are quite obviously not camelCased.

On Sunday, 6 February 2022 at 14:00:15 UTC, Paul Backus wrote:
> On Sunday, 6 February 2022 at 13:40:00 UTC, Paolo Invernizzi wrote:
>> On Sunday, 6 February 2022 at 13:33:53 UTC, Paul Backus wrote:
>>>
>>> @mustUse is a user-defined attribute, and the official style guide says that names of UDAs should be camelCased:
>>>
>>> https://dlang.org/dstyle.html#naming_udas
>>
>> ... This matches conventions of the built in attributes like @safe,  __@nogc__  ...
>
> Presumably this is referring to the part about the first letter being lower-case, since the built-in attributes are quite obviously not camelCased.

While I like a lot and welcome the addition of this attribute (so thank you!), I humbly  ask to reconsider using   the full lowercase alternative instead of camel case.

Let's conform with the other built-in attributes listed into the specs of the language, avoiding what would be another special case to remember.

On Sunday, 6 February 2022 at 14:32:31 UTC, Paolo Invernizzi wrote:
> While I like a lot and welcome the addition of this attribute (so thank you!), I humbly  ask to reconsider using   the full lowercase alternative instead of camel case.
>
> Let's conform with the other built-in attributes listed into the specs of the language, avoiding what would be another special case to remember.

There is precedent for compiler-recognized UDAs using camelCase in core.attribute.gnuAbiTag [1], as well as the various LDC-specific attributes [2]. So no matter what I choose here, it will be inconsistent with something.

If you strongly prefer the lower-case version, you can always rename it in your own code:

    import core.attribute: mustuse = mustUse;

    @mustuse struct MyStruct
    {
        // ...
    }

[1]: https://druntime.dpldocs.info/core.attribute.gnuAbiTag.html
[2]: https://wiki.dlang.org/LDC-specific_language_changes#Attributes

On Sunday, 6 February 2022 at 14:56:42 UTC, Paul Backus wrote:
> On Sunday, 6 February 2022 at 14:32:31 UTC, Paolo Invernizzi wrote:
>> While I like a lot and welcome the addition of this attribute (so thank you!), I humbly  ask to reconsider using   the full lowercase alternative instead of camel case.
>>
>> Let's conform with the other built-in attributes listed into the specs of the language, avoiding what would be another special case to remember.
>
> There is precedent for compiler-recognized UDAs using camelCase in core.attribute.gnuAbiTag [1], as well as the various LDC-specific attributes [2]. So no matter what I choose here, it will be inconsistent with something.
>
> If you strongly prefer the lower-case version, you can always rename it in your own code:
>
>     import core.attribute: mustuse = mustUse;
>
>     @mustuse struct MyStruct
>     {
>         // ...
>     }
>
> [1]: https://druntime.dpldocs.info/core.attribute.gnuAbiTag.html
> [2]: https://wiki.dlang.org/LDC-specific_language_changes#Attributes

That's fine, I will not insist more, hoping not to see in the future it extended as a function attribute ... you know ...

int foo() @nogc @safe @mustUse etc etc ...

On Sunday, 6 February 2022 at 15:17:35 UTC, Paul Backus wrote:
> On Sunday, 6 February 2022 at 14:44:40 UTC, Ola Fosheim Grøstad wrote:
>> On Sunday, 6 February 2022 at 13:33:53 UTC, Paul Backus wrote:
>>>
>>> @mustUse is a user-defined attribute, and the official style guide says that names of UDAs should be camelCased:
>>
>> It is kinda confusing to call it a user-defined attribute if it is recognized by the compiler.
>
> Compiler-recognized UDAs are an established feature of D. See [`core.attribute`][1] for more examples.
>
>> I dislike the camel case as well, and the name is less clear than "nodiscard" in my opinion.
>
> I suppose you'll have to take that up with Walter, since he's the one who vetoed "nodiscard".
>
> To be honest, though, I can see where he's coming from. When writing DIP 1038, I made a conscious effort to avoid using the term "non-`@nodiscard`", due to the double negative. With a positively-phrased name like `@mustUse`, that problem disappears.
>
> [1]: https://druntime.dpldocs.info/core.attribute.html

@hold (or @held) ? donwannaopenacanofworms ... my last post really :-P

(btw, It's a great companion for sumtype! thank you again!)

On Sunday, 6 February 2022 at 15:24:17 UTC, Paolo Invernizzi wrote:
> @hold (or @held) ? donwannaopenacanofworms ... my last post really :-P

Pretend that you are a beginning D programmer, and you come across one of the following declarations while reading someone else's code:

    @use struct Result
    {
        // ...
    }

    @hold struct Result
    {
        // ..
    }

    @mustUse struct Result
    {
        // ...
    }

You have never seen any of these attributes before in your life, and there are no comments explaining what they mean--all you have to go on is the name. Which name is are you most likely to guess the correct meaning for: "use", "hold", or "mustUse"?