Skip to content

Conversation

groldan
Copy link
Member

@groldan groldan commented Aug 26, 2024

Dealing with long[] everywhere and knowing it means {x,y,z} is tiring.

Introducing a TileIndex abstraction improves the semantics, and at the same time allows to save memory on TileObject by storing the coordinates as internal long,long,int fields and saving the object reference to a long array.


This is a proposal. Can we please stop using long[] everywhere?
If accepted, there would be more places to get rid of long arrays
and introduce higher level abstractions (e.g. TileRangeInterator)

Dealing with `long[]` everywhere and knowing it means `{x,y,z}` is
tiring.

Introducing a `TileIndex` abstraction improves the semantics, and at the
same time allows to save memory on TileObject by storing the
coordinates as internal long,long,int fields and saving the object
reference to a `long` array.

---

> This is a **proposal**. Can we please stop using `long[]` everywhere?
> If accepted, there would be more places to get rid of `long` arrays
> and introduce higher level abstractions (e.g. `TileRangeInterator`)
@groldan groldan force-pushed the split_tileobject_xyz branch from 8b494e4 to 27e5d87 Compare August 27, 2024 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant