Adam Wilson
Adam Wilson
I can confirm that this still exists on OSX 10.12 with DMD 2.072.1. Does anybody have a work-around?
I use AES256_SSSE3 which appears to be missing from the plain build.
I don't, but the above snippets are sufficient to reproduce the error.
@lempiji Did you attempt to build both python and C# bindings into the same library? Right now both the python bindings and the C# bindings insert the DllMain. The workaround...
The simplest thing to do is to marshal DateTime/SysTime as an ISO 8601 string. In C# a struct can be either blittable and non-blittable, only blittable types can be used...
Because it's an identical amount of code either way and solves the TimeZone problem.
Because strings are immutable in both languages it was easier to treat them not as pointers from a marshalling standpoint, instead they are marshalled as byte-arrays and copied into memory...
Here are the reasons to use strings: - ISO 8601 strings the standard for date interchange, it is guaranteed to work correctly and precisely across languages that implement it. Both...
The immutable nature of strings make them a special case as far ownership goes because copies are by definition owned by whichever GC created them. I've attached a PR that...
At this point this is expected. As we discussed earlier I did not implement templates in order to keep the scope to something that was shippable in a reasonable time-frame....