You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Really liking the library so far, but had one question. Looking at the implementation, it seems like every component gets an auto-incrementing ID, which is used to shift bits to create a component bit mask. Am I right in thinking that if a bigint max value is roughly 2^53, geotic allows for a maximum of 53 component types that can be registered? This still seems like a good amount for most projects, but wanted to see if there was a suggested workaround for adding more.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi @Aedalus, I believe using BigInt has different bitwise limitations than int. I remember thinking about this during implementation, and I believe I tested it in chrome (this was some time ago).
Regardless, it might be smart to use a different library dedicated to bitwise operations, see #51
Really liking the library so far, but had one question. Looking at the implementation, it seems like every component gets an auto-incrementing ID, which is used to shift bits to create a component bit mask. Am I right in thinking that if a bigint max value is roughly 2^53, geotic allows for a maximum of 53 component types that can be registered? This still seems like a good amount for most projects, but wanted to see if there was a suggested workaround for adding more.
Thanks!
The text was updated successfully, but these errors were encountered: