It seems the intention of code like
guard !isLoading else { return }
but it also seems that there can be multiple instances and no tracking of a current loading state against an URL inside a single cache instance
is to prevent image loading twice or whatever, however, if we have a view that uses the same image several times, opening Charles shows the images is attempting to be loaded more than once.
It seems the intention of code like
guard !isLoading else { return }but it also seems that there can be multiple instances and no tracking of a current loading state against an URL inside a single cache instance
is to prevent image loading twice or whatever, however, if we have a view that uses the same image several times, opening Charles shows the images is attempting to be loaded more than once.