On Sunday, 29 May 2022 at 01:35:23 UTC, frame wrote:
Is there a compiler switch to catch this kind of error?
```d
ulong v = 1;
writeln(v > -1);
```
IMHO the compiler should bail a warning if it sees a logic
comparison between signed and unsigned / different integer
sizes. There is 50% chance
On Monday, 30 May 2022 at 13:15:12 UTC, bauss wrote:
Good luck convincing Walter that this is a mistake :)
I don't think this is a matter of convincing or changing the
behavior, I think that a flag for this case (If not exist) should
be added as a warning.
A language where some people use t
On Monday, 30 May 2022 at 13:15:12 UTC, bauss wrote:
Good luck convincing Walter that this is a mistake :)
Well, I'm not talking about this is a mistake, just a C-thing I
think. I wouldn't even ask him about that since it's in the spec.
If I could I would just clone a DMD build, disable out
On Sunday, 29 May 2022 at 01:35:23 UTC, frame wrote:
Is there a compiler switch to catch this kind of error?
```d
ulong v = 1;
writeln(v > -1);
```
IMHO the compiler should bail a warning if it sees a logic
comparison between signed and unsigned / different integer
sizes. There is 50% chance
On Sunday, 29 May 2022 at 01:35:23 UTC, frame wrote:
Is there a compiler switch to catch this kind of error?
```d
ulong v = 1;
writeln(v > -1);
```
IMHO the compiler should bail a warning if it sees a logic
comparison between signed and unsigned / different integer
sizes. There is 50% chance
Is there a compiler switch to catch this kind of error?
```d
ulong v = 1;
writeln(v > -1);
```
IMHO the compiler should bail a warning if it sees a logic
comparison between signed and unsigned / different integer sizes.
There is 50% chance that a implicit conversion was not intended.
