On Monday, 22 January 2018 at 06:15:24 UTC, Dmitry Olshansky
wrote:
On Sunday, 21 January 2018 at 17:28:13 UTC, Andres Clari wrote:
Hi, is there any way to get from the GC all allocated objects,
so I can see their size and find where I'm leaking memory? Or
perhaps a good tool to help with this
On Sunday, 21 January 2018 at 17:28:13 UTC, Andres Clari wrote:
Hi, is there any way to get from the GC all allocated objects,
so I can see their size and find where I'm leaking memory? Or
perhaps a good tool to help with this issue...
I tried building my program with "profile-gc" but I got an
On Sunday, 21 January 2018 at 20:46:56 UTC, Timon Gehr wrote:
On 21.01.2018 21:20, Mark wrote:
Just realized that I commented out the creation of the BST
new link: https://dpaste.dzfl.pl/ce620cbee919
'in' means 'const scope', but it seems you need references that
are allowed to mutate the i
On 21.01.2018 21:20, Mark wrote:
Just realized that I commented out the creation of the BST
new link: https://dpaste.dzfl.pl/ce620cbee919
'in' means 'const scope', but it seems you need references that are
allowed to mutate the incoming items. Remove the 'in' attribute from the
parameters a
Just realized that I commented out the creation of the BST
new link: https://dpaste.dzfl.pl/ce620cbee919
Hello,
I re wrote my old BST. This one is far more complete and clean.
However, It fails my final unittest when I try to stick a class
in as its type.
Link: https://dpaste.dzfl.pl/95e1ae49b25b
Ive done this type of thing before, but it is giving me this
error:
BinarySearchTree.d(30): Erro
On Sunday, 21 January 2018 at 16:22:33 UTC, Marc wrote:
But libraries has this defined:
extern(C) int callback(void*, int, char** , char**){
Just rename one of the functions. It is really bad form to have
extern(C) functions have a common word like this exactly because
they share a namespac
On 2018-01-20 00:16, rumbu wrote:
According to this
(https://dlang.org/spec/hash-map.html#static_initialization) this is
correct static initialization for AA:
immutable RoundingMode[string] ibmRounding =
[
">" : RoundingMode.towardPositive,
"<" : RoundingMode.towardNegative,
"0
Hi, is there any way to get from the GC all allocated objects, so
I can see their size and find where I'm leaking memory? Or
perhaps a good tool to help with this issue...
I tried building my program with "profile-gc" but I got an
invalid MemoryOperationError with no stack trace... so no luck
I was using a Sqlite3 library then I included another library
that started the conflict. From what I could tell, it seems it's
another Sqlite3 engine that the included library uses. The link
error is:
.dub\build\application-debug-windows-x86-dmd_2076-E7D07B7BDA58325E30A3C637FC043AFE\foo.obj(y
My understanding is, currently read DIP1000 as:
"NB: this DIP is out of sync with -dip1000 compiler switch
implementation ...".
My own current problem fits well in this thread:
I want to push forward support of -dip1000 in phobos, testing
each module's compatibility with -dip1000 individually
On Sunday, 21 January 2018 at 10:27:05 UTC, Mike Franklin wrote:
On Sunday, 21 January 2018 at 10:04:36 UTC, Mike Franklin wrote:
What is/was `transition=safe`? I can't find any documentation
on it.
Adding -transition=? to the dmd (v2.078.0) command line doesn't
show safe listed.
My unders
On Sunday, 21 January 2018 at 10:04:36 UTC, Mike Franklin wrote:
What is/was `transition=safe`? I can't find any documentation
on it.
Well, I found
http://forum.dlang.org/post/gquxgusfhyigirfpe...@forum.dlang.org
But, didn't really clear much up for me.
Mike Franklin wrote:
And what does "NB" mean?
"nota bene". used as "pay attention to the following".
I found the following statement in the DIP1000 document
(https://github.com/dlang/DIPs/blob/master/DIPs/DIP1000.md)
NB: this DIP is out of sync with -transition=safe
implementation available in dmd and pending a rewrite. Most key
points still apply though.
What is/was `transition=safe`? I c
15 matches
Mail list logo