← Back to index | Original Bugzilla link

Bug 6764 – IFTI fails on typesafe variadic function over static array with non IntegerLiteral length

Status: RESOLVED
Resolution: FIXED
Severity: minor
Priority: P2
Component: dmd
Product: D
Version: D2
Platform: All
OS: All
Creation time: 2011-10-03T23:14:00Z
Last change time: 2015-06-09T05:11:36Z
Keywords: patch, rejects-valid
Assigned to: nobody
Creator: verylonglogin.reg

Comments

Comment #0 by verylonglogin.reg — 2011-10-03T23:14:20Z

--- enum N = 1; //use const for D1 alias size_t[N] T; //workaround void f()(T arr...) { } void g()(size_t[1] arr...) { } void h()(size_t[N] arr...) { } void main() { f(0); //good g(0); //good h!()(0); //good h(0); //Error: template main.f() does not match any function template declaration } ---

Comment #1 by k.hara.pg — 2011-10-04T17:38:03Z

https://github.com/D-Programming-Language/dmd/pull/431

Comment #2 by github-bugzilla — 2012-08-28T00:38:48Z

Commits pushed to master at https://github.com/D-Programming-Language/dmd https://github.com/D-Programming-Language/dmd/commit/ef9c344118925cb362be0fe14a18590556e7c9dd Issue 6764 - IFTI fails on typesafe variadic function over static array with non IntegerLiteral length https://github.com/D-Programming-Language/dmd/commit/a5c56ac957035efc142ad4a1123c6b138f1e4a15 Merge pull request #431 from 9rnsr/fix6764 Issue 2296 & 6764 - IFTI fails on typesafe variadic function

Comment #3 by k.hara.pg — 2012-09-10T07:35:48Z

Fixed in D2.

Comment #4 by yebblies — 2013-11-16T22:56:09Z

Closing because D1 is no longer supported.

Comment #5 by verylonglogin.reg — 2013-11-17T04:31:06Z

Why FIXED instead of WONTFIX?

Comment #6 by yebblies — 2013-11-17T04:38:07Z

Because it was fixed for D2...

Comment #7 by verylonglogin.reg — 2013-11-17T04:41:07Z

(In reply to comment #6) > Because it was fixed for D2... And now it's D1 bug. You have to change title and "Version" or WONTFIX it. I changed title as the fix is rather fresh.

Comment #8 by mailnew4ster — 2013-11-17T04:41:42Z

There are lots of ICEs which are D1 only. Should these be marked as fixed, too? Issue 2325, issue 3865, issue 4129, issue 4504, issue 5211, issue 7883, issue 8014, issue 8865, issue 9366, issue 9439, issue 9908, issue 10217.

Comment #9 by yebblies — 2013-11-17T04:44:53Z

(In reply to comment #7) > (In reply to comment #6) > > Because it was fixed for D2... > > And now it's D1 bug. You have to change title and "Version" or WONTFIX it. I > changed title as the fix is rather fresh. You do that if it makes you happy. (In reply to comment #8) > There are lots of ICEs which are D1 only. > Should these be marked as fixed, too? > > Issue 2325, issue 3865, issue 4129, issue 4504, issue 5211, issue 7883, issue > 8014, issue 8865, issue 9366, issue 9439, issue 9908, issue 10217. I don't plan on closing ices and wrong code. You'd have to ask Andrei for the official stance.

Comment #10 by verylonglogin.reg — 2013-11-17T04:54:01Z

(In reply to comment #9) > (In reply to comment #7) > > (In reply to comment #6) > > > Because it was fixed for D2... > > > > And now it's D1 bug. You have to change title and "Version" or WONTFIX it. I > > changed title as the fix is rather fresh. > > You do that if it makes you happy. So am I the only one here who think resolution of an unfixed D1 issue as FIXED is a bad idea?

Comment #11 by yebblies — 2013-11-17T05:03:28Z

(In reply to comment #10) > (In reply to comment #9) > > (In reply to comment #7) > > > (In reply to comment #6) > > > > Because it was fixed for D2... > > > > > > And now it's D1 bug. You have to change title and "Version" or WONTFIX it. I > > > changed title as the fix is rather fresh. > > > > You do that if it makes you happy. > > So am I the only one here who think resolution of an unfixed D1 issue as FIXED > is a bad idea? ... the bug has been fixed for all currently supported versions of D. I really don't care what's in closed reports.