1. assertEquals vs. assertArrayEquals
Currently, the reporting of failures is the main reason for
having two functions.
For short arrays of short items, the difference looks best using
'assertEquals'.
With 'assertArrayEquals', you'll only get the index and the first
mismatch reported.
For mu
On Thursday, 13 June 2013 at 00:00:05 UTC, Juan Manuel Cabo wrote:
I'm glad that dunit was of use to you and that the fork
went well.
I'm sorry I couldn't follow up on it.
--jm
We are much obliged for you providing the foundation.
Your announcement and SiegeLord's port of Tango were the start
On Thursday, 13 June 2013 at 00:10:56 UTC, bearophile wrote:
In that code have you felt the lack for some built-in feature
for D (Like some introspection, some hooks, some dynamic
feature, etc)?
D(1)Unit has a 'fixturebuilder' that iterates over 'ModuleInfo'
and 'localClasses', and finally fo
On Thu, 2013-06-13 at 00:15 +0200, Mario Kroeplin wrote:
> Here is the 'dunit' mentioned in the talk by Stefan Rohe:
> https://github.com/linkrope/dunit
>
> D-stroy ;-)
One immediate issue, why have assertArrayEquals distinct from
assertEquals, surely assertEqual can be a template with variants f
Mario Kroeplin:
Here is the 'dunit' mentioned in the talk by Stefan Rohe:
https://github.com/linkrope/dunit
D-stroy ;-)
In that code have you felt the lack for some built-in feature for
D (Like some introspection, some hooks, some dynamic feature,
etc)?
Maybe you can replace code like th
On 06/12/2013 07:15 PM, Mario Kroeplin wrote:
> Here is the 'dunit' mentioned in the talk by Stefan Rohe:
> https://github.com/linkrope/dunit
>
> D-stroy ;-)
I'm glad that dunit was of use to you and that the fork
went well.
I'm sorry I couldn't follow up on it.
--jm
Here is the 'dunit' mentioned in the talk by Stefan Rohe:
https://github.com/linkrope/dunit
D-stroy ;-)
