[Issue 5683] Calling .clear on a fresh associative array causes subsequent segfault

2011-08-04 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5683


d...@dawgfoto.de changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE


--- Comment #4 from d...@dawgfoto.de 2011-08-04 02:19:06 PDT ---
*** This issue has been marked as a duplicate of issue 6433 ***

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 5683] Calling .clear on a fresh associative array causes subsequent segfault

2011-07-19 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5683


d...@dawgfoto.de changed:

   What|Removed |Added

 CC||ratchet.fr...@gmail.com


--- Comment #2 from d...@dawgfoto.de 2011-07-19 09:21:33 PDT ---
*** Issue 5816 has been marked as a duplicate of this issue. ***

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 5683] Calling .clear on a fresh associative array causes subsequent segfault

2011-07-19 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5683


d...@dawgfoto.de changed:

   What|Removed |Added

 CC||d...@dawgfoto.de


--- Comment #3 from d...@dawgfoto.de 2011-07-19 12:54:13 PDT ---
A quickfix if urgently needed by anybody is to add a static init method to the
template AA structure.

struct AssociativeArray(Key, Value)
{
static Value[Key] init() @property
{
void* p;
return *cast(Value[Key]*)(p);
}
}

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 5683] Calling .clear on a fresh associative array causes subsequent segfault

2011-04-04 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=5683


Iain Buclaw ibuc...@ubuntu.com changed:

   What|Removed |Added

 CC||ibuc...@ubuntu.com


--- Comment #1 from Iain Buclaw ibuc...@ubuntu.com 2011-04-04 12:15:29 PDT ---
This is a horrible bug with .init, and nothing to do with .clear.

Same code but without the external call:

void main() {
  int[char] test;
  test = typeof(test).init;
  test['x'] = 42;
}

What seems to be happening is that the address of the constructor is being
assigned (ie: test = test_init) when it should *really* be a direct
assignment.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---