On Monday, 17 May 2021 at 16:54:07 UTC, mw wrote:
I filed the issue here (still no response yet):
https://github.com/ariovistus/pyd/issues/152
It's fixed now: pyd version >= 0.14.1
On Tuesday, 18 May 2021 at 16:27:13 UTC, Alain De Vos wrote:
After each } i write a ;
And let the compiler tell me it is an empty instruction.
What are the general rules where ; is not needed after a }
Is `;` ever needed after a `}`?
I guess in `void delegate() dg = { writeln!"Hello World"; };
After each } i write a ;
And let the compiler tell me it is an empty instruction.
What are the general rules where ; is not needed after a }
On Tuesday, 18 May 2021 at 12:15:25 UTC, Alain De Vos wrote:
Something like:
import X.Y.Z:mapresult ;
You don't. The types returned by map, filter, and other
algorithms are not public. They're "Voldemort", or anonymous,
types. Instances aren't generally intended to be stored, but
rather to b
Something like:
import X.Y.Z:mapresult ;
On Tuesday, 18 May 2021 at 10:14:26 UTC, PinDPlugga wrote:
But what I do not understand is why opEquals is necessary and
where in the implementation of toHash it plays its role? Since
area1 and area2 have different static arrays of Points I
understand why `typeid(points).getHash(&points)` would
In the solution to one of the exercises in Programming in D the
unittests fail with respect to the toHash implementation.
Here is a link to the full solution provided:
https://run.dlang.io/gist/99ddf791f86aaa9d333d032166aadcb9?args=-unittest%20-main
and the link to the relevant section in the b
For a number it's best to have something you know how many bytes
it takes in memory.
Knowing the number of bytes in memory is a good thing.
