Nate Martin

yes _but_ i have a lot of internal changes i'm working on right now that may shift the internal architecture a bit, so i'm holding off for the moment. changes...

seems like a bug! thanks for reporting, i'll work on a fix ASAP

@luetkemj it seems this error indicates that `newWorld` does not know about a component that `world` knows about. components are normally automatically registered with worlds when they are either added...

hi @grorp, thanks for creating the issue! this feature is doable, i shall add it to my to-do list :+1: > Are arrays really more expensive than objects? they only...

this would be consistent with the current API: ```js const innerArray = Component.array[entityID][arrayID] ``` the other way around doesn't make sense imo. what does `14` represent in `Component.array[14]` and what...

the semantics that i have prefered are such that we use the entityID for accessing a value for a specific entity from a component. ```js const x = Position.x[eid] ```...

this is neat! but there are 2 issues, correct me if i'm wrong: 1. the compiler will obfuscate the real underlying type of `TypedArray` and its own suite of methods...

@EnderShadow8 here is a screenshot of what I meant (with your typings applied):  all of these highlighted properties (`flat`, `push`, `pop`, etc) do not exist on TypedArrays, despite the...

hahah okay ignore me, you're right @EnderShadow8. i misunderstood. i'm also in the middle of a refactor and confused myself. i have been trying to figure out how to limit...

> > if you could limit these calls in your typings that would be great, but i also want to somehow prevent it in raw JS as well > >...