I am trying out autowrap to build a D library for Python.
After I ran "dub build" which builds mylib.so and try to import
it in Python interpreter, I get:
"ImportError: dynamic module does not define module export
function (PyInit_libautowrap_mylib)"
Which means the library was build for
Inside
https://github.com/nordlow/phobos-next/
doing
dub build --compiler=dmd --build=unittest
works but
dub test --compiler=dmd
fails as
Generating test runner configuration 'phobos-next-test-library'
for 'library' (library).
Performing "unittest" build using /usr/bin/dmd for
On Monday, 15 June 2020 at 18:48:04 UTC, Per Nordlöw wrote:
This doesn't seem like an intuitive interface to me. I would
like `dub dustmite` to work directly inside the source tree by
creating a temporary copy of the root directory of a clean git
repo checkout (excluding the .git* files) where
On Tuesday, 16 June 2020 at 06:19:51 UTC, Joel wrote:
I've tired different unit test libraries, but they jump out on
errors instead of just adding to failed numbers.
I'm thinking like this:
```
@("dummy");
unittset {
0.shouldEqual(0);
1.shouldEqual(2);
2.shouldEqual(3);
}
```
Test:
On Tuesday, 16 June 2020 at 07:39:20 UTC, Luis wrote:
On Tuesday, 16 June 2020 at 06:19:51 UTC, Joel wrote:
[...]
I understand that where the trivial test code is placed, must
be something more complex being tested.
@("dummy test 1");
unittest {
/// Some test code that runs fine
}
On 6/12/20 3:02 PM, adnan338 wrote:
> So there are multiple "download finished" message producers, and one
> consumer of those messages. Furthermore, that producer has a callback
> that triggers an UI object.
That's almost exactly what I do in some of my programs. I use
std.concurrency and the
On Tuesday, 16 June 2020 at 06:19:51 UTC, Joel wrote:
I've tired different unit test libraries, but they jump out on
errors instead of just adding to failed numbers.
I'm thinking like this:
```
@("dummy");
unittset {
0.shouldEqual(0);
1.shouldEqual(2);
2.shouldEqual(3);
}
```
Test:
On Tuesday, 16 June 2020 at 06:19:51 UTC, Joel wrote:
I've tired different unit test libraries, but they jump out on
errors instead of just adding to failed numbers.
I'm thinking like this:
```
@("dummy");
unittset {
0.shouldEqual(0);
1.shouldEqual(2);
2.shouldEqual(3);
}
```
Test:
I've tired different unit test libraries, but they jump out on
errors instead of just adding to failed numbers.
I'm thinking like this:
```
@("dummy");
unittset {
0.shouldEqual(0);
1.shouldEqual(2);
2.shouldEqual(3);
}
```
Test: dummy
test passed line 10: 0 is equal to 0
test failed
