On Tuesday, 17 July 2012 at 17:19:31 UTC, Jonathan M Davis wrote:
On Tuesday, July 17, 2012 10:47:50 Andrei Alexandrescu wrote:
On 7/17/12 4:41 AM, monarch_dodra wrote:
On Monday, 16 July 2012 at 22:42:47 UTC, Andrei Alexandrescu
wrote:
Wow, this is awesome. Did you discover that by
On Monday, 16 July 2012 at 22:42:47 UTC, Andrei Alexandrescu
wrote:
Wow, this is awesome. Did you discover that by inspection or by
testing? I think a malicious input range would be a great
tool for assessing which algorithms fail on input ranges.
Andrei
The first I discovered testing with
On 7/17/12 4:41 AM, monarch_dodra wrote:
On Monday, 16 July 2012 at 22:42:47 UTC, Andrei Alexandrescu
wrote:
Wow, this is awesome. Did you discover that by inspection or by
testing? I think a malicious input range would be a great tool for
assessing which algorithms fail on input ranges.
On Tuesday, July 17, 2012 10:47:50 Andrei Alexandrescu wrote:
On 7/17/12 4:41 AM, monarch_dodra wrote:
On Monday, 16 July 2012 at 22:42:47 UTC, Andrei Alexandrescu
wrote:
Wow, this is awesome. Did you discover that by inspection or by
testing? I think a malicious input range would be a
I had a discussion recently about the proper use of save when
passing to foreach or algorithms, as well as read the thread
about algorithms being hard to use. It was concluded this the
problem mostly came from:
a) Lack of proper testing.
b) Missing or inaccurate input type checking.
I decided
On 7/16/12 6:43 AM, monarch_dodra wrote:
I had a discussion recently about the proper use of save when passing
to foreach or algorithms, as well as read the thread about algorithms
being hard to use. It was concluded this the problem mostly came from:
a) Lack of proper testing.
b) Missing or
