Disclaimer: this was written well before Dicebots reply, but not submitted, so some have already been said.
Am 26.12.2013 13:01, schrieb David Nadlinger:
Hi all,
I'm currently working on getting vibe.d to run on LDC.
I've fixed (or rather worked around, as it's actually the frontend messing things up) that linking problem and also fixed two other bugs I stumbled across when building vibe.d with a debug version of LDC. Right now, the merge-2.064 branch with my open pull requests builds a few of the examples fine on Linux x86_64, and all the basics seem to be working fine (I couldn't observe any of the crashes mentioned in the various vibe.d bug reports). The HTTP benchmark examples seem to perform a bit better than when built with DMD, but that was just a very cursory test.
That's great news! I'll add LDC builds to my CI server when it's ready.
Now, two questions:
1) Is there a comprehensive test suite I can run to ensure that there are no more miscompilations/… left in the basic structure? How can I easily run the unit test using dub (vibe.d being a library project)?
With GIT master of DUB, "dub test" should work. For older versions there is a special "unittest" configuration ("dub --config=unittest --build=unittest").
The unit tests are not really suited for testing I/O and fiber related things, but the benchmark examples should normally be sufficiently complex to catch most issues there. For template/CTFE/linker stress testing, the vibed.org and code.dlang.org websites are also living quite on the cutting edge (at least for DMD).
2) I recall seeing some promising performance numbers for vibe.d quite a while back, although I don't remember where exactly that was. Are there any benchmark implementations I could try to get some "interesting" numbers?
What I used was "weighttp" on two separate linux machines connected by GbE. The client machine had to have a powerful CPU or "weighttp" wasn't able to saturate the "bench-http-server". Currently it's a little unclear how well the performance actually is, as it hasn't been benchmarked for a while and there were some changes in critical parts that may have had an influence. There is also a recent thread about this.