Simen kjaeraas wrote:
> "dmd a b -unittest" works. "dmd b a -unittest" does not.
This may explain a problem that I hit recently.
I had had all of a program's code in a single file. Then I started
pulling classes to their respective source files one by one. As I did
that, of course I compiled
On Tue, 08 Jun 2010 21:10:54 +0900, Masahiro Nakagawa wrote:
> On Tue, 08 Jun 2010 19:39:43 +0900, Simen kjaeraas
> wrote:
>
>> Simen kjaeraas wrote:
>>
>>> Lars T. Kyllingstad wrote:
>>>
FWIW, I've run across the same error, while writing code that had
nothing
to do with tuples
On Tue, 08 Jun 2010 19:39:43 +0900, Simen kjaeraas
wrote:
Simen kjaeraas wrote:
Lars T. Kyllingstad wrote:
FWIW, I've run across the same error, while writing code that had
nothing
to do with tuples. And I've seen others complaining about it too. It
seems to be a rather elusive bug
On Tue, 08 Jun 2010 12:56:04 +0200, Simen kjaeraas wrote:
> Lars T. Kyllingstad wrote:
>> That's consistent with my experiences too. It seems to be triggered by
>> a Phobos unittest.
>>
>> Still, I can't reproduce it with your test case. Which DMD version are
>> you using?
>
> 2.045. Actually,
Lars T. Kyllingstad wrote:
That's consistent with my experiences too. It seems to be triggered by a
Phobos unittest.
Still, I can't reproduce it with your test case. Which DMD version are
you using?
2.045. Actually, I can't reproduce it now either. Ah, found the problem.
"dmd a b -unittest"
Lars T. Kyllingstad wrote:
I'm not sure I understand this. Do you then import a and b into another
module to reproduce the error? This doesn't do it for me...
As the bug report says: "dmd -unittest a b"
--
Simen
On Tue, 08 Jun 2010 12:39:43 +0200, Simen kjaeraas wrote:
> Simen kjaeraas wrote:
>
>> Lars T. Kyllingstad wrote:
>>
>>> FWIW, I've run across the same error, while writing code that had
>>> nothing
>>> to do with tuples. And I've seen others complaining about it too. It
>>> seems to be a rat
On Tue, 08 Jun 2010 12:31:50 +0200, Simen kjaeraas wrote:
> Lars T. Kyllingstad wrote:
>
>> FWIW, I've run across the same error, while writing code that had
>> nothing to do with tuples. And I've seen others complaining about it
>> too. It seems to be a rather elusive bug in Phobos.
>
> This
Simen kjaeraas wrote:
Lars T. Kyllingstad wrote:
FWIW, I've run across the same error, while writing code that had
nothing
to do with tuples. And I've seen others complaining about it too. It
seems to be a rather elusive bug in Phobos.
This has now been tracked down to the importing of
Lars T. Kyllingstad wrote:
FWIW, I've run across the same error, while writing code that had nothing
to do with tuples. And I've seen others complaining about it too. It
seems to be a rather elusive bug in Phobos.
This has now been tracked down to the importing of std.typecons in two
includ
On Tue, 08 Jun 2010 03:29:05 +0200, Simen kjaeraas wrote:
> Sounds stupid, don't it?
> 123456789012345678901234567890123456789012345678901234567890123456789012
> Carrying in my hat my trusty foo, a std.typecons.Tuple!(float), I want
> to use it as a parameter to a function taking non-tuple paramet
Simen kjaeraas wrote:
I guess what I'm asking for here is, is there a way to do what I want?
Hm, it seems the problem was not where I thought it was. However, this
is getting curiouser and curiouser.
--
Simen
Sounds stupid, don't it?
123456789012345678901234567890123456789012345678901234567890123456789012
Carrying in my hat my trusty foo, a std.typecons.Tuple!(float), I want
to use it as a parameter to a function taking non-tuple parameters, i.e.
a single float. foo.tupleof gives me an unwieldy conglom
13 matches
Mail list logo
