On Sunday, 4 June 2023 at 22:14:59 UTC, Richard (Rikki) Andrew
Cattermole wrote:
On 05/06/2023 9:20 AM, ryuukk_ wrote:
Then this needs to be fixed asap, unittest needs to work for
the flags user will use
There is nothing to fix.
You literally do not have any of the druntime code needed to
On 05/06/2023 9:20 AM, ryuukk_ wrote:
Then this needs to be fixed asap, unittest needs to work for the flags
user will use
There is nothing to fix.
You literally do not have any of the druntime code needed to handle
ModuleInfo and hence call via it.
Nor do you have the entry point handled
On Sunday, 4 June 2023 at 20:43:17 UTC, Richard (Rikki) Andrew
Cattermole wrote:
Unittests require some mechanism to execute them.
Druntime provides this capability by default.
You can do it manually by using ``__traits(getUnitTests)`` to
get access to the symbols.
Personally I just use
Unittests require some mechanism to execute them.
Druntime provides this capability by default.
You can do it manually by using ``__traits(getUnitTests)`` to get access
to the symbols.
Personally I just use full D for unittests.
Neither:
```
extern(C) int foo() {
return 4;
}
unittest {
assert(foo() != 4, "!= Assert triggered.");
assert(foo() == 4, "== Assert triggered.");
}
```
Nor:
```
int foo() {
return 4;
}
unittest {
assert(foo() != 4, "!= Assert triggered.");
assert(foo() == 4, "== Assert
