I've been curious for a while how close GDC2 and LDC2 are to being ready
for production use. Are the test suite results posted publicly for
either of these? Other than that, is there anything else other than
building and testing for myself that would give me a good idea of where
these libraries stand?

I've been curious for a while how close GDC2 and LDC2 are to being ready
for production use. Are the test suite results posted publicly for
either of these? Other than that, is there anything else other than
building and testing for myself that would give me a good idea of where
these libraries stand?

I've been curious for a while how close GDC2 and LDC2 are to being ready
for production use. Are the test suite results posted publicly for
either of these? Other than that, is there anything else other than
building and testing for myself that would give me a good idea of where
these libraries stand?

The typical reply is "they're already fully production ready, it just depends
on what you need". Seriously though, people have different kind of requirements
for production ready products. These kind of questions just start yet another
public debate of the basic definitions of terms.

I've been curious for a while how close GDC2 and LDC2 are to being ready
for production use. Are the test suite results posted publicly for either
of these? Other than that, is there anything else other than building and
testing for myself that would give me a good idea of where these libraries
stand?

I know that Iain has been working through Brad's testsuite for DMD on 64 bit
GDC, but I don't think he has the results being generated in any automated
fashion. I believe 32 bit is pretty much production ready but 64 bit has
some issues, but he'd know that better than, well, anyone.

I've been curious for a while how close GDC2 and LDC2 are to being ready
for production use. Are the test suite results posted publicly for
either of these? Other than that, is there anything else other than
building and testing for myself that would give me a good idea of where
these libraries stand?

I don't think it is "dsmicha's production" ready. Though if you write D2 code
conservatively there should be little reason why things should go wrong. :~)
Unittests that fail in the D2 testsuite can be found here:
https://bitbucket.org/goshawk/gdc/src/6e40c9c42f6e/testsuite/Makefile#cl-103
With 64bit, all the same tests pass with the exception to some vararg related
tests passing structs/unions.
However, the testsuite can really only been taken with a pinch of salt, and
certainly doesn't cover everything the language allows you to do.

I've been curious for a while how close GDC2 and LDC2 are to being ready
for production use. Are the test suite results posted publicly for
either of these? Other than that, is there anything else other than
building and testing for myself that would give me a good idea of where
these libraries stand?

I don't think it is "dsmicha's production" ready. Though if you write D2 code
conservatively there should be little reason why things should go wrong. :~)

LOL. I mean, this really made me laugh out loud. I see I've gotten a
(probably well-deserved) reputation around here for pushing compilers to
the limit and finding every bug imaginable. Yeah, std.parallelism is
horribly broken with GDC on Windows. I haven't tested on Linux yet. As
far as I can tell the brokenness is deterministic, so it's very unlikely
to be latent concurrency bugs. The funny thing is that most of the bugs
I've filed against GDC have been culled from (of all things) a
statistics library I wrote. Same with most of the bugs I found in the
DMD 64-bit port. How a statistics library could possibly be so good for
finding compiler bugs that the test suites miss, I'll never know.

This is the kind of thing I'm looking for. The biggest reason I wanted
this info is so I know what the known defects are and don't have to
waste time reducing and filing bug reports for bugs where there are tons
of probably related unit test failures already.
BTW, my statistics library now passes all its unit tests on 64-bit Linux
as of last time I checked. There's still one bug that only occurs on
32, and it looks like a rather nightmarish cross-module bug in a 15,000
line codebase. I haven't gotten around to reducing/filing it yet.

However, the testsuite can really only been taken with a pinch of salt, and
certainly doesn't cover everything the language allows you to do.

I've been curious for a while how close GDC2 and LDC2 are to being ready
for production use. Are the test suite results posted publicly for
either of these? Other than that, is there anything else other than
building and testing for myself that would give me a good idea of where
these libraries stand?

I don't think it is "dsmicha's production" ready. Though if you write D2 code
conservatively there should be little reason why things should go wrong. :~)

LOL. I mean, this really made me laugh out loud. I see I've gotten a
(probably well-deserved) reputation around here for pushing compilers to
the limit and finding every bug imaginable. Yeah, std.parallelism is
horribly broken with GDC on Windows. I haven't tested on Linux yet. As
far as I can tell the brokenness is deterministic, so it's very unlikely
to be latent concurrency bugs. The funny thing is that most of the bugs
I've filed against GDC have been culled from (of all things) a
statistics library I wrote. Same with most of the bugs I found in the
DMD 64-bit port. How a statistics library could possibly be so good for
finding compiler bugs that the test suites miss, I'll never know.