fluent-asserts
fluent-asserts copied to clipboard
gedaiu
DLang fluent assertions done right
maybe the problems caused by some _sharedStaticCtor_ ? ``` Thread 1 "" received signal SIGSEGV, Segmentation fault. 0x0000555555ea28d1 in _D13fluentasserts4core6expect6Expect6__ctorMFNcNeSQBwQBk10evaluation15ValueEvaluationxAyaxmAyaZSQDqQDeQDcQCy (this=0x7fffd9638500, value=..., fileName=..., line=506, prependText="") at /.dub/packages/fluent-asserts-1.0.0/fluent-asserts/source/fluentasserts/core/expect.d:25 25 evaluation.id =...
/.dub/packages/fluent-asserts-1.0.0/fluent-asserts/source/fluentasserts/core/operations/registry.d(81): There are no matching assert operations. Register any of `std.checkedint.Checked!(long, std.checkedint.Abort).std.checkedint.Checked!(long, std.checkedint.Abort).lessThan`, `*.*.lessThan` to perform this assert.
This assert used works in v0.13.3: ``` Assert.equal(1003200.0, 1003200); ``` but in v1.0.0: ``` /.dub/packages/fluent-asserts-1.0.0/fluent-asserts/source/fluentasserts/core/base.d(506): 1.0032e+06 should equal 1003200. 1.0032e+06 is not equal to 1003200. Diff: 1[+.]0032[+e+]0[-0][+6] Expected:1003200 Actual:1.0032e+06 ```...
with Version 0.14.0.alpha8 `opEquals()` is not honoured anymore when asserting equality. It worked prior version 0.14. See the following MWE: ```D import std.stdio; import fluent.asserts; void main() {} class Thing...
Tested with 0.14.0-alpha.7 I got the following results: ```D import std.stdio; import fluent.asserts; import std.range; import std.algorithm; void main() { writeln("Edit source/app.d to start your project."); } unittest { auto...
Error: template instance fluentasserts.core.base.Assert.opDispatch!("notLessThan", string, string) error instantiating
``` #!/usr/bin/env dub /+ dub.sdl: dependency "fluent-asserts" version="~>0.13.0" dependency "dateparser" version="~>3.0.3" +/ import fluent.asserts; void main() { int[] wa = new int[1442]; int[] da = new int[6953]; auto dl =...
Hi, I use this library not just in unittest, but also as a replacement for the D built-in `assert` in the normal code. But I want to turn off these...
Hi, Just wonder if we can add a func to report total count of assertion failure upto the calling point?, e.g. Assert.count()? So the user can check the total assertion...
Morning, It looks like Arrays (std.container.array) data types will cause test to not compile because the destructor is marked with @system. The error message looks similar to this: `@safe function...
