[Issue 7874] [CTFE] internal error: unsupported assignment (x OP= y) = z
https://issues.dlang.org/show_bug.cgi?id=7874 --- Comment #7 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/D-Programming-Language/dmd https://github.com/D-Programming-Language/dmd/commit/8be17b6a7b715faeb9321afba21623eaf5cca87c fix Issue 7874 - [CTFE] internal error: unsupported assignment (x OP= y) = z Fixed in PR #4227 (22badb69bd07f013b96383ae4e07dd93cf12d115). --
[Issue 7874] [CTFE] internal error: unsupported assignment (x OP= y) = z
https://issues.dlang.org/show_bug.cgi?id=7874 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --
[Issue 7874] [CTFE] internal error: unsupported assignment (x OP= y) = z
https://issues.dlang.org/show_bug.cgi?id=7874 Kenji Hara k.hara...@gmail.com changed: What|Removed |Added Keywords||pull --- Comment #6 from Kenji Hara k.hara...@gmail.com --- Fixed in 2.067a git-head, by: https://github.com/D-Programming-Language/dmd/pull/4227 Test case addition: https://github.com/D-Programming-Language/dmd/pull/4319 --
[Issue 7874] [CTFE] internal error: unsupported assignment (x OP= y) = z
http://d.puremagic.com/issues/show_bug.cgi?id=7874 --- Comment #5 from timon.g...@gmx.ch 2012-04-22 09:44:30 PDT --- That is not what this bug report is about. One can never argue that an ICE and spitting out of internal IR are good things. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 7874] [CTFE] internal error: unsupported assignment (x OP= y) = z
http://d.puremagic.com/issues/show_bug.cgi?id=7874 --- Comment #3 from timon.g...@gmx.ch 2012-04-21 11:44:38 PDT --- (In reply to comment #2) Actually, the first example gives on 2.059 PS E:\DigitalMars\dmd2\samples dmd -c bug bug.d(2): Error: function bug.foo (int x) is not callable using argument types () bug.d(2): Error: expected 1 function arguments, not 0 That is a typo. Fixed test case: int foo(int x){return ++x=1;} enum bar = foo(0); -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 7874] [CTFE] internal error: unsupported assignment (x OP= y) = z
http://d.puremagic.com/issues/show_bug.cgi?id=7874 --- Comment #4 from SomeDude lovelyd...@mailmetrash.com 2012-04-21 14:36:01 PDT --- One could argue that the fact that such code is rejected is rather a good thing. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 7874] [CTFE] internal error: unsupported assignment (x OP= y) = z
http://d.puremagic.com/issues/show_bug.cgi?id=7874 Don clugd...@yahoo.com.au changed: What|Removed |Added CC||clugd...@yahoo.com.au Summary|[CTFE] CTFE internal error: |[CTFE] internal error: |unsupported assignment |unsupported assignment (x ||OP= y) = z --- Comment #1 from Don clugd...@yahoo.com.au 2012-04-17 01:43:48 PDT --- Applies to many forms of op= assignment, including some cases of ref assignment. Eg. int foo(int[] x){ auto b = (x~=x)=[1,2,3]; return 3; } enum bar = foo([7,5]); -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---