Re: Odd stacktrace: Access Violation in object.TypeInfo_Interface.getHash

2015-09-07 Thread Fra via Digitalmars-d-learn
On Monday, 7 September 2015 at 11:04:20 UTC, Nicholas Wilson wrote: On Monday, 7 September 2015 at 08:55:31 UTC, Fra wrote: I encountered a runtime error in my code and all I can get (even in debug mode) is the following stacktrace: object.Error@(0): Access Violation 0x0051C30

Odd stacktrace: Access Violation in object.TypeInfo_Interface.getHash

2015-09-07 Thread Fra via Digitalmars-d-learn
I encountered a runtime error in my code and all I can get (even in debug mode) is the following stacktrace: object.Error@(0): Access Violation 0x0051C308 in const(nothrow @trusted uint function(const(void*))) object.TypeInfo_Interface.getHash 0x0058D2C0 in D6engine5world5worl

Re: Classes and @disable this()

2015-02-08 Thread fra via Digitalmars-d-learn
On Sunday, 8 February 2015 at 16:22:36 UTC, fra wrote: Missclick... Anywya: class Something { @disable this(); this(int i) {} } produces an undefined reference error. I guess it has to do with classes implicitly inheriting from Object, and Object defining a this(), and @disable telling th

Classes and @disable this()

2015-02-08 Thread fra via Digitalmars-d-learn
I just realized that you cannot define a disabled "default" constructor for classes: writing code like this will give a linker error class Something {

Re: Fast array copy. SIMD manual or automatic?

2015-02-08 Thread fra via Digitalmars-d-learn
On Saturday, 7 February 2015 at 06:30:32 UTC, tcak wrote: I have two char arrays at the size of 16KB. I will copy a part of data between them again and again. arrayA[0 .. dataLen] = arrayB[0 .. dataLen]; Does the compiler generate code that uses SIMD operations (128-bits memory copy) automat

Re: Tracing down core.exception.InvalidMemoryOperationError

2014-07-28 Thread fra via Digitalmars-d-learn
On Monday, 28 July 2014 at 22:13:56 UTC, Joakim wrote: On Monday, 28 July 2014 at 13:31:08 UTC, Martin Drasar via Digitalmars-d-learn wrote: On 28.7.2014 14:09, Joakim via Digitalmars-d-learn wrote: More broadly speaking, it is thrown whenever certain memory operations are attempted while the G