Several image requests read and write the same in-memory cache dictionary at the same time. It crashes now and then, and the logs show the same URL downloaded twice. If you fixed it with an actor instead of a lock, which state would you put inside the actor?
Put both mutable pieces of state inside the actor, the dictionary of finished images and the list of requests currently downloading, and allow access from outside only through await; then the data race from concurrent writes to the dictionary disappears at compile time.
ConcurrencyShort answerBasics
This code gets called from several threads, and count comes out lower than expected. Can…
#actor #data-race
TestingShort answerExpert
How do you reproduce or detect a data race in concurrent code that uses actors and Tasks?
#actor #data-race
ConcurrencyShort answerExpert
This image cache actor built with Swift Concurrency sometimes sends two network requests…
#actor
ConcurrencyMultiple choiceAdvanced
Under Swift 6 strict concurrency, which of the following are treated as Sendable (or…
#actor