Optimize for more efficient and predictable performance by changing Array to CountiguousArray #825
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Replace those declared as Array<ViewController> with Contiguous Array<UIViewController> type that is stored in contiguous blocks of memory.
Replace those declared as Array<ViewController> with Contiguous Array<UIViewController> type that is stored in contiguous blocks of memory.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I changed to use ContiguousArray< UIViewController > type to store UIViewControllers in a contiguous block of memory.
When using a large number of UIViewControllers as tabs, I think that using ContiguousArray will yield more predictable performance compared to Array.
The changed source file is:
for Example:
References