Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread forkit via Digitalmars-d-announce
On Tuesday, 8 February 2022 at 02:57:29 UTC, forkit wrote: I would prefer @must_use over @mustUse, for example (althouhgh i prefer @mustuse to both of these, since the underscore is not really needed in this case). my argument for the above, is: The problem with using camelCase on

Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread Walter Bright via Digitalmars-d-announce
On 2/7/2022 6:21 PM, Paul Backus wrote: On Monday, 7 February 2022 at 23:40:38 UTC, Walter Bright wrote: On 2/6/2022 9:05 PM, forkit wrote: only to have the compiler complain, that its' actually @mustUse I have to agree. All D keywords and imports and compiler-recognized attributes are

Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread forkit via Digitalmars-d-announce
On Tuesday, 8 February 2022 at 02:21:37 UTC, Paul Backus wrote: I guess core.attribute.gnuAbiTag sneaked in behind your back, huh? Anyway, I'm happy to change it if that's your call, although it would have been nice to have caught this before the DIP was officially accepted. actually, I

Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread forkit via Digitalmars-d-announce
On Tuesday, 8 February 2022 at 01:53:17 UTC, forkit wrote: also, the use of the word 'must' in any programming language, needs careful consideration. 'mustuse' has the potential to invite mass 'mustuse' demonstrations! 'nodiscard' suggests somewhat more 'autonomy', and would achieve a

Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread Paul Backus via Digitalmars-d-announce
On Monday, 7 February 2022 at 23:40:38 UTC, Walter Bright wrote: On 2/6/2022 9:05 PM, forkit wrote: only to have the compiler complain, that its' actually @mustUse I have to agree. All D keywords and imports and compiler-recognized attributes are lower case, @mustuse should be consistent

Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread forkit via Digitalmars-d-announce
On Tuesday, 8 February 2022 at 01:40:38 UTC, forkit wrote: I often say to my cat 'what are you doing' .. but what i really mean is 'don't do that'. by avoiding negation, I'm probably just confusing my cat as to what i really meant. mustuse -> I must use it? Why must i use it? How must I

Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread forkit via Digitalmars-d-announce
On Tuesday, 8 February 2022 at 01:25:52 UTC, Walter Bright wrote: Sorry, all those negations made my brain explode. P.S. English has examples of negation issues, such as: "I could care less." which makes no sense at all, until you realize it's just a shortened version of "I couldn't care

Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread Walter Bright via Digitalmars-d-announce
On 2/6/2022 7:14 AM, Daniel N wrote: However by choosing "use" we could avoid the entire discussion about which case to use... "mustuse" is much more greppable.

Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread Walter Bright via Digitalmars-d-announce
On 2/7/2022 5:10 PM, forkit wrote: Suppose I don't want to 'use it'. That should be allowed, as long as I don't discard it. With mustuse, I'm being told I can't discard it, and that i must use it. Sorry, all those negations made my brain explode. P.S. English has examples of negation issues,

Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread forkit via Digitalmars-d-announce
On Monday, 7 February 2022 at 23:38:11 UTC, Walter Bright wrote: Anytime you find yourself writing not-nohow, not-noway, etc., it's time to redesign the state of the variables. Try to organize logic so ! is not necessary. I mean, try to organize logic so ! is absent. But sometimes that

Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread forkit via Digitalmars-d-announce
On Monday, 7 February 2022 at 23:38:11 UTC, Walter Bright wrote: Andrei once asked me for scientific evidence that negations are cognitively more difficult for human brains to understand. I didn't have it at the time, but did eventually find it and forwarded it to Andrei, who was satisfied

Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread Walter Bright via Digitalmars-d-announce
On 2/6/2022 9:05 PM, forkit wrote: only to have the compiler complain, that its' actually @mustUse I have to agree. All D keywords and imports and compiler-recognized attributes are lower case, @mustuse should be consistent with that.

Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread Walter Bright via Digitalmars-d-announce
On 2/6/2022 7:17 AM, Paul Backus wrote: 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.

Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread forkit via Digitalmars-d-announce
On Monday, 7 February 2022 at 13:55:40 UTC, Paul Backus wrote: I've seen similar sentiments expressed many times before, in other contexts. Every time, there are some who insist that the new name will never feel natural to them, and they will never let go of the old name. And every time,

Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread Paul Backus via Digitalmars-d-announce
On Monday, 7 February 2022 at 05:12:39 UTC, forkit wrote: no amount of replies will change anything ;-) .. people will still 'think' @nodiscard, but have to 'remember' it's actually @mustuse, but oops.. no... it's @mustUse.. I do not expect anything from my feedback ;-) .. I'm just

Re: DIP 1038--"@mustUse" (formerly "@noDiscard")--Accepted

2022-02-07 Thread bauss via Digitalmars-d-announce
On Monday, 7 February 2022 at 05:09:23 UTC, Paul Backus wrote: On Monday, 7 February 2022 at 05:05:27 UTC, forkit wrote: my only concern is the capital U, in @mustUse This seems a little inconsistent with current attributes?? e.g: nogc nothrow inout https://dlang.org/spec/attribute.html