[Issue 8374] One missed array literal interpretation as int[2]

2022-12-17 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=8374 Iain Buclaw changed: What|Removed |Added Priority|P2 |P3 --

[Issue 8374] One missed array literal interpretation as int[2]

2016-10-15 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=8374 Andrei Alexandrescu changed: What|Removed |Added Keywords||bootcamp

[Issue 8374] One missed array literal interpretation as int[2]

2013-11-26 Thread d-bugmail
https://d.puremagic.com/issues/show_bug.cgi?id=8374 --- Comment #7 from bearophile_h...@eml.cc 2013-11-26 05:08:07 PST --- (In reply to comment #5) The problem is, while [10,20] converts to int[2], int[2] converts to int[]. int[] is picked as the common type. I'm not entirely sure we want

[Issue 8374] One missed array literal interpretation as int[2]

2013-11-26 Thread d-bugmail
https://d.puremagic.com/issues/show_bug.cgi?id=8374 --- Comment #8 from yebblies yebbl...@gmail.com 2013-11-27 00:13:24 EST --- (In reply to comment #7) The current situation is a little more subtle: int[2] foo1() { int[2] a; return true ? a : [1, 2]; // OK } const(int[2])

[Issue 8374] One missed array literal interpretation as int[2]

2013-11-25 Thread d-bugmail
https://d.puremagic.com/issues/show_bug.cgi?id=8374 --- Comment #5 from yebblies yebbl...@gmail.com 2013-11-26 02:30:24 EST --- The problem is, while [10,20] converts to int[2], int[2] converts to int[]. int[] is picked as the common type. I'm not entirely sure we want to change that. --

[Issue 8374] One missed array literal interpretation as int[2]

2013-11-25 Thread d-bugmail
https://d.puremagic.com/issues/show_bug.cgi?id=8374 --- Comment #6 from bearophile_h...@eml.cc 2013-11-25 07:42:13 PST --- (In reply to comment #5) The problem is, while [10,20] converts to int[2], int[2] converts to int[]. int[] is picked as the common type. I'm not entirely sure we want

[Issue 8374] One missed array literal interpretation as int[2]

2013-01-16 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8374 yebblies yebbl...@gmail.com changed: What|Removed |Added CC||yebbl...@gmail.com ---

[Issue 8374] One missed array literal interpretation as int[2]

2012-07-10 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8374 Walter Bright bugzi...@digitalmars.com changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 8374] One missed array literal interpretation as int[2]

2012-07-10 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8374 timon.g...@gmx.ch changed: What|Removed |Added Status|RESOLVED|REOPENED CC|

[Issue 8374] One missed array literal interpretation as int[2]

2012-07-10 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8374 --- Comment #3 from bearophile_h...@eml.cc 2012-07-10 17:49:56 PDT --- (In reply to comment #1) The type of [1,2] is int[], not int[2]. Usually in my bug reports I add some cases where the code works, to avoid troubles like this one.