ecs: ECS fixes #334
No reviewers
Labels
No labels
CI
all
basisu
blog
bug
build
contributor-friendly
core
correctness
deferred
dev
direct3d-headers
docs
driver-os-issue
duplicate
dxcompiler
editor
examples
experiment
feature-idea
feedback
flac
freetype
gamemode
gkurve
glfw
gpu
gpu-dawn
harfbuzz
help welcome
in-progress
infrastructure
invalid
libmach
linux-audio-headers
long-term
mach
mach.gfx
mach.math
mach.physics
mach.testing
model3d
needs-triage
object
opengl-headers
opus
os/linux
os/macos
os/wasm
os/windows
package-manager
priority
proposal
proposal-accepted
question
roadmap
slipped
stability
sysaudio
sysgpu
sysjs
validating-fix
vulkan-zig-generated
wayland-headers
website
wontfix
wrench
www
x11-headers
xcode-frameworks
zig-update
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
hexops/mach!334
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two small fixes for the ECS
copy(), which had thesrc_rowanddst_rowarguments supplied in the wrong ordersetComponent()andremoveComponent()functions, caused bygetOrPut()on the hash map sometimes invalidating the archetype retrieved byarchetypeByID().I haven't made a minimal reproducible example for the second bug, it doesn't show up under all circumstances, in my use it showed up when 'enough' stuff was added to the ECS, which must have made
getOrPutContext()more likely to invalidate the pointer.Perhaps there is a better way to rewrite the usage of
archetypein the functions, this is just the minimal change that stops things crashing.Thanks! I have more major changes to this ECS library coming soon. Interesting to hear you are using it for something! In general (and as you have found) I would say it's not ready for that yet :)