August 13, 2020
https://issues.dlang.org/show_bug.cgi?id=21151

kinke <kinke@gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|wrong-code                  |spec
           Hardware|x86_64                      |All
                 OS|Linux                       |All

--- Comment #10 from kinke <kinke@gmx.net> ---
Removing the wrong-code tag, as code adhering to the spec isn't wrong.

--
August 13, 2020
https://issues.dlang.org/show_bug.cgi?id=21151

--- Comment #11 from kinke <kinke@gmx.net> ---
FWIW, in C# this is an error:

long a = -5000;
ulong b = 2;
long c = a / b; // Operator '/' is ambiguous on operands of type 'long' and
'ulong'

--
August 13, 2020
https://issues.dlang.org/show_bug.cgi?id=21151

--- Comment #12 from mw <mingwu@gmail.com> ---
for the additional reference, the forum discussion is here:

https://forum.dlang.org/thread/rdrqedmbknwrppbfixll@forum.dlang.org

Now both Java and C# did it more correct than D.


"""
At least I want a warning message, even with a turn-on command-line switch is
fine, I personally will turn it on all the time, silently performing this
conversions is horrible.



In many area of the language design, we need to make a choice between: correctness v.s. raw performance.

But at least we also need *explicit* visible warning message after we've made that choice:

-- especially warnings about *correctness* when the choice was made favoring
performance
-- if the choice was made favoring correctness, user will notice the
performance when the program runs.


Personally, I will favor correctness over performance in my program design decisions: make it correct first, and faster later; you never know before-hand where your program's bottleneck is.

I'm sure you know the famous quote:

"Premature optimization is the root of all evil!"

"""

--
December 17, 2022
https://issues.dlang.org/show_bug.cgi?id=21151

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2

--
1 2
Next ›   Last »