August 14, 2021

On Friday, 13 August 2021 at 21:10:38 UTC, Steven Schveighoffer wrote:

>

Well, subtracting the length doesn't do much, you aren't actually accessing the array block, you are just changing the reference (which lives in thread-local storage). I kind of feel like the whole entity table thing is not correct anyway. Did you (Mike) also comment out the did call? Because that looks more suspicious to me. What it is doing is going through all the entities from the removed one on and setting their id to 1 less. HOWEVER, it's not actually moving the entities down in the array.

I suspected the did function first, but the issue persisted when I commented out the call in the destructor. I didn't know what to think when I found that commenting out the .length deprecation eliminated it.

>

I suspect there is a memory access violation or some other issue that's causing it to crash rather than exit normally.

It's not crashing. It's hanging.

August 14, 2021

On Friday, 13 August 2021 at 21:36:35 UTC, Ruby The Roobster wrote:

>

Thank you very much. The program runs successfully now.

You've got another potential issue you should be aware of. You've name a member of your Skeleton as init. This may cause issues at some point, as every type in D has a default init property, even structs. You shouldn't use that name in any type you define.

1 2
Next ›   Last »