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
Motivated by Issue #71 it might be desirable to have a single class of Location and use that to cover all types. This removes type confusion, removes explicit type conversion which can cause runtime errors, and it ultimately allows us to later be more better at handling memory allocation by using an Object pool.
In another experimental branch I have found a way to merge all Location classes into a single Location class. As of now, it requires some clean up, but might be a great starting point for discussion.
The text was updated successfully, but these errors were encountered:
Motivated by Issue #71 it might be desirable to have a single class of Location and use that to cover all types. This removes type confusion, removes explicit type conversion which can cause runtime errors, and it ultimately allows us to later be more better at handling memory allocation by using an Object pool.
In another experimental branch I have found a way to merge all Location classes into a single Location class. As of now, it requires some clean up, but might be a great starting point for discussion.
The text was updated successfully, but these errors were encountered: