http://www.digitalmars.com/d/1.0/changelog.html
http://ftp.digitalmars.com/dmd.1.058.zip


http://www.digitalmars.com/d/2.0/changelog.html
http://ftp.digitalmars.com/dmd.2.043.zip

Thanks to the many people who contributed to this update!

Thank you for the release and your work, and thank you to Don for all the bug fixes.
I will need some more time to test this release better. In the meantime, is it possible to use BigInts into an AA? This gives a Range violation:

import std.bigint: BigInt;
void main() {
    BigInt[BigInt] aa;
    aa[BigInt(1)]++;
}

Bye,
bearophile

Le 09/04/10 13:35, bearophile a écrit :
> Thank you for the release and your work, and thank you to Don for all the bug fixes.
> I will need some more time to test this release better. In the meantime, is it possible to use BigInts into an AA? This gives a Range violation:
>
> import std.bigint: BigInt;
> void main() {
>      BigInt[BigInt] aa;
>      aa[BigInt(1)]++;
> }
>
> Bye,
> bearophile

Maybe this is the same problem as with:

import std.variant;
void main() {
    Variant[string] aa;
    aa["one"] = 1;
}

Bug 2451?

bearophile wrote:
> Thank you for the release and your work, and thank you to Don for all the bug fixes.
> I will need some more time to test this release better. In the meantime, is it possible to use BigInts into an AA? This gives a Range violation:
> 
> import std.bigint: BigInt;
> void main() {
>     BigInt[BigInt] aa;
>     aa[BigInt(1)]++;
> }
> 
> Bye,
> bearophile


Could this have anything to do with BigInt not having a toHash() function?

-Lars

Now I have tested this release a little better, it seems to work well. I have to say two things:

1) The bug 3911 was a mix of two different bugs, Don has fixed one of them, so I have closed the bug 3911 and I have opened a new cleaned bug report, number 4075:
http://d.puremagic.com/issues/show_bug.cgi?id=3911
http://d.puremagic.com/issues/show_bug.cgi?id=4075

Because this code generates an error still:
auto foo() { return 0; }
enum int _ = foo();
void main() {}



2) Bug 3972 is not fixed, it's open still. The error message produced is not good yet. I have added a comment at the bottom:
http://d.puremagic.com/issues/show_bug.cgi?id=3972

In the situation I've shown in 3972 a better error message is the two error messages (or something similar):

spam.d(2): Error: module 'test' has mismatched file name 'spam.d'.
foo.d(2): Error: module 'bar' has mismatched file name 'foo.d'.

Bye,
bearophile

bearophile wrote:
> In the situation I've shown in 3972 a better error message is the two error
> messages (or something similar):
> 
> spam.d(2): Error: module 'test' has mismatched file name 'spam.d'. foo.d(2):
> Error: module 'bar' has mismatched file name 'foo.d'.


The error is not a mismatched file name, which is perfectly legitimate in D. The error is two different files have the same module name.

bearophile wrote:
> Now I have tested this release a little better, it seems to work well. I have to say two things:
> 
> 1) The bug 3911 was a mix of two different bugs, Don has fixed one of them, so I have closed the bug 3911 and I have opened a new cleaned bug report, number 4075:

Please don't clutter the announce newsgroup with bug reports.
And in general, do NOT put multiple bugs in one report. In particular, it's worth saying this to everyone: if something causes a compiler segfault or an internal compiler error, ALWAYS put it in its own report. In > 95% of cases it's a different bug, even if it looks the same as something else.

Don wrote:
> Please don't clutter the announce newsgroup with bug reports.
> And in general, do NOT put multiple bugs in one report. In particular, it's worth saying this to everyone: if something causes a compiler segfault or an internal compiler error, ALWAYS put it in its own report. In > 95% of cases it's a different bug, even if it looks the same as something else.

Don's right. But it is ok to reply with a link to a bugzilla report.

Walter Bright:

Thank you for your answer.

> The error is not a mismatched file name, which is perfectly legitimate in D.

Do you mean that in D it is OK to have a file named "foo.d" with inside it at the top written "module bar;" ? What's the rationale behind this? (I don't like this).


>The error is two different files have the same module name.<

Maybe I am missing something, but:
- there is a module "bar" in the file named "foo.d"
- and there is the module "test" in the file named "spam.d".
All four names are distinct, there are no name duplication (and the imports can't change this basic fact).

Bye,
bearophile

bearophile wrote:
> Walter Bright:
> 
> Thank you for your answer.
> 
>> The error is not a mismatched file name, which is perfectly legitimate in
>> D.
> 
> Do you mean that in D it is OK to have a file named "foo.d" with inside it at
> the top written "module bar;" ?

Yes.

> What's the rationale behind this? (I don't like this).

The flexibility comes in handy now and then.