[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= Iain Buclaw changed: What|Removed |Added Priority|P2 |P4 --

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= Boris Carvajal changed: What|Removed |Added CC||boris...@gmail.com --

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= Paul Backus changed: What|Removed |Added CC||snarwin+bugzi...@gmail.com --- Comment #23

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= --- Comment #22 from deadalnix --- At the very least, 1 -> true should match as an implicit conversion, not an exact match (in which case, one gets an overload resolution error rather than a bug). That would still be bad, but that would at least not

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= deadalnix changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= Paul Backus changed: What|Removed |Added CC||deadal...@gmail.com --- Comment #20 from Paul

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= --- Comment #19 from Илья Ярошенко --- This bugs causes critical data bugs for various libraries such as Algebraic/Variant types, JSON and other data libraries. Shame. --

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= Dennis changed: What|Removed |Added CC||ilyayaroshe...@gmail.com --- Comment #18 from

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= --- Comment #16 from Mike Franklin --- A DIP has been submitted to address this issue: https://github.com/dlang/DIPs/blob/master/DIPs/DIP1015.md A PR implementing the DIP can be found at https://github.com/dlang/dmd/pull/7310 --

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= Nick Treleaven changed: What|Removed |Added See Also||https://issues.dlang.org/sh

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= Mike changed: What|Removed |Added CC||slavo5...@yahoo.com

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= Nick Treleaven changed: What|Removed |Added CC||n...@geany.org --- Comment

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= --- Comment #13 from Denis Shelomovskij verylonglogin@gmail.com --- (In reply to Denis Shelomovskij from comment #12) Also this issue has to terrible consequences: * two terrible consequences 1. `f(bool)` is preferred over `f(T)(T)` A

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= --- Comment #14 from Jonathan M Davis issues.dl...@jmdavisprog.com --- (In reply to Denis Shelomovskij from comment #12) Also this issue has to terrible consequences: 1. `f(bool)` is preferred over `f(T)(T)` 2. expressions like `4 - 3` triggers the

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= Denis Shelomovskij verylonglogin@gmail.com changed: What|Removed |Added CC|

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

https://issues.dlang.org/show_bug.cgi?id= hst...@quickfur.ath.cx changed: What|Removed |Added CC||hst...@quickfur.ath.cx --- Comment

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

http://d.puremagic.com/issues/show_bug.cgi?id= yazan.dab...@gmail.com changed: What|Removed |Added CC||yazan.dab...@gmail.com ---

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

http://d.puremagic.com/issues/show_bug.cgi?id= --- Comment #9 from Don clugd...@yahoo.com.au 2013-04-29 01:19:47 PDT --- I don't have strong feelings about this, but I don't know how to defend the current behaviour. Implicit conversion from int to bool is indeed rather odd. Do we really

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

http://d.puremagic.com/issues/show_bug.cgi?id= --- Comment #7 from Martin Nowak c...@dawg.eu 2013-04-28 04:05:07 PDT --- (In reply to comment #6) If you simply made it so that integer literals didn't implicitly convert to bool, that would solve this particular problem. There's really no

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

http://d.puremagic.com/issues/show_bug.cgi?id= --- Comment #8 from Jonathan M Davis jmdavisp...@gmx.com 2013-04-28 06:48:32 PDT --- Integers do NOT implicitly convert to bool (see comment 5) You're right. In the general case, they don't, but VPR makes it so that it can happen (and not

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

http://d.puremagic.com/issues/show_bug.cgi?id= --- Comment #1 from Kenji Hara k.hara...@gmail.com 2013-04-27 11:24:52 PDT --- In here, following mechanism would work for overload resolution. 0. Integer literal 0 and 1 have `int` type, and it does not exactly match to bool and long. 1. bool

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

http://d.puremagic.com/issues/show_bug.cgi?id= Kenji Hara k.hara...@gmail.com changed: What|Removed |Added Keywords||pull --- Comment #2

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

http://d.puremagic.com/issues/show_bug.cgi?id= Walter Bright bugzi...@digitalmars.com changed: What|Removed |Added CC|

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

http://d.puremagic.com/issues/show_bug.cgi?id= --- Comment #4 from Kenji Hara k.hara...@gmail.com 2013-04-27 13:23:21 PDT --- Walter, I can understand your concern. But I think it would not be so big. Because the possibility of extending basic type set is not so much in the future. Keeping

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

http://d.puremagic.com/issues/show_bug.cgi?id= Martin Nowak c...@dawg.eu changed: What|Removed |Added CC||c...@dawg.eu --- Comment

[Issue 9999] Integer literal 0 and 1 should prefer integer type in overload resolution

http://d.puremagic.com/issues/show_bug.cgi?id= Jonathan M Davis jmdavisp...@gmx.com changed: What|Removed |Added CC|