CURL Wrapper: Congratulations Next up: std.serialize

[Brad Anderson]

On Wed, Dec 28, 2011 at 10:11 PM, Jonathan M Davis <jmdavisProg at gmx.com>wrote:

> On Wednesday, December 28, 2011 23:07:51 Jacob Carlborg wrote:
> > I think it is, don't know what others think. What it does is it catches
> > AssertErrors so other unit tests can continue to run and then gives a
> > nice report at the end.
>
> I'm against it. I think that the compiler/runtime should be fixed so that
> each
> unit test block is run in a module even if one fails. That would solve the
> problem quite nicely IMHO, and that's already _supposed_ to be how it
> works.
> It just isn't properly implemented in that regard yet. And I'm against
> unittest blocks running any code after a single failure. So, I don't think
> that any additional unit testing framework is necessary.
>
> - Jonathan M Davis
>

Forgive me if this is a silly question but a conversation in IRC got me
wondering if compiler could check for shared/__gshared use (and any other
thread unsafe operation) in each unittest and run those that aren't using
them concurrently? Obviously not all at once but at least more than one at
a time (perhaps set through user configuration).

Regards,
Brad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20111229/ecbcd9ca/attachment.html>