SizeSpec experiment #2287
Draft
SizeSpec experiment #2287
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
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.
An experiment with one particular approach. Would need more work but should be enough for discussion.
I wondered what a flexible API would look like for more generic deferred requests - not just those for
ImageView. I liked the idea of size resolution becoming asynchronous, but the main challenge was when to do it. I ultimately landed on it happening during request creation, as size information is important to consider for caching.This has a few consequences, (I had to put
runBlockingin a few places), but maybe the idea is sound. I dunno. Food for thought at any rate.