<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Concurrency on Jijnasa</title><link>https://jijnasa.blog/tags/concurrency/</link><description>Recent content in Concurrency on Jijnasa</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 14 May 2026 10:00:00 -0500</lastBuildDate><atom:link href="https://jijnasa.blog/tags/concurrency/index.xml" rel="self" type="application/rss+xml"/><item><title>Understanding @isolated(any)</title><link>https://jijnasa.blog/posts/understanding-isolated-any/</link><pubDate>Thu, 14 May 2026 10:00:00 -0500</pubDate><guid>https://jijnasa.blog/posts/understanding-isolated-any/</guid><description>A @MainActor class passes a closure to a protocol method. The closure fires on a task and the closure is called within the Task. Here is how @isolated(any) solves the problem of landing in the closure in a different context instead of the same context which created it!.</description></item></channel></rss>