Menu
Search

Forums

Forum Index

Thread overview
tuple(tuple(1)) fails to compile, but tuple(tuple(1),1) works
Sep 20, 2012
timotheecour
Sep 20, 2012
timotheecour
Sep 20, 2012
Timon Gehr
September 20, 2012
Gravatar of timotheecourPosted by timotheecourReply
timotheecour
Gravatar of timotheecour


Reply
inconsistent:
auto a1=tuple(tuple(1));//CT error
auto a2=tuple(tuple(1),1);//works

bug?
September 20, 2012
Gravatar of timotheecourPosted by timotheecour
in reply to timotheecour		Reply
timotheecour
Gravatar of timotheecour
Posted in reply to timotheecour


Reply
On Thursday, 20 September 2012 at 23:03:34 UTC, timotheecour wrote:
> inconsistent:
> auto a1=tuple(tuple(1));//CT error
> auto a2=tuple(tuple(1),1);//works
>
> bug?

I filed it here: http://d.puremagic.com/issues/show_bug.cgi?id=8702
September 20, 2012
Gravatar of Timon GehrPosted by Timon Gehr
in reply to timotheecour		Reply
Timon Gehr
Gravatar of Timon Gehr
Posted in reply to timotheecour


Reply
On 09/21/2012 01:04 AM, timotheecour wrote:
> inconsistent:
> auto a1=tuple(tuple(1));//CT error
> auto a2=tuple(tuple(1),1);//works
>
> bug?

Yes. In general, if there is a compile time error other than a static
assertion failure that points to Phobos code, you can assume that it is
a library bug.