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
This is an optimization that might want to be considered in the future.
The current approach with lists is that for every data item in the list, one list entry object is created. Modern lists as for example in Android use a recycling-based list principle. This basically means that instead of creating a list entry object for every data item, we only create enough to fill the screen and maybe some more as buffers. Then we fill in these same list entry objects with different data items, essentially recycling them.
That said, our lists are usually not that long and any data item is too big to be initialized for filling the entries with, so it might be better to just keep it as it is
The text was updated successfully, but these errors were encountered:
This is an optimization that might want to be considered in the future.
The current approach with lists is that for every data item in the list, one list entry object is created. Modern lists as for example in Android use a recycling-based list principle. This basically means that instead of creating a list entry object for every data item, we only create enough to fill the screen and maybe some more as buffers. Then we fill in these same list entry objects with different data items, essentially recycling them.
That said, our lists are usually not that long and any data item is too big to be initialized for filling the entries with, so it might be better to just keep it as it is
The text was updated successfully, but these errors were encountered: