Osna.FM
The DAX started trading Wednesday with modest gains. The benchmark index was calculated at approximately 24,410 points by 9:30 AM, marking a 0.1 percent increas... https://news.osna.fm/?p=47031 | #news #await #crucial #dax #earnings
Habr[Перевод] Async/Await в C# это синтаксический сахар для конечного автомата
Перевод статьи, посвящённой устройству конечного автомата асинхронных методов. Разбор основных понятий, декомпилированный код с подробными комментариями, раскрытие секретов магии асинхронности и подробная схема.
https://habr.com/ru/articles/1035442/
#асинхронность #async #await #c# #конечный_автомат #awaiter #c#net #taskbuilder #statemachine
The U.S. stock markets ended Wednesday with mixed results. The Dow Jones Industrial Average closed at 49,693 points, marking a 0.1 percent decrease compared to... https://news.osna.fm/?p=45886 | #news #await #economy #global #investors
N-gated Hacker News🥳🎉 Oh wow, #ClojureScript finally got async/await! 🚀 Just 1.12.145 releases later, they've caught up to JavaScript's 2017 #tech. 🎩✨ So innovative, it's practically cutting-edge... if you're living in the past. 📅🔄
https://clojurescript.org/news/2026-05-07-release #async #await #JavaScript #innovation #news #HackerNews #ngated
https://clojurescript.org/news/2026-05-07-release #async #await #JavaScript #innovation #news #HackerNews #ngated
Hacker NewsClojureScript Gets Async/Await
https://clojurescript.org/news/2026-05-07-release
#HackerNews #ClojureScript #Async #Await #FunctionalProgramming #JavaScript #News #Development
robrichhttps://www.linkedin.com/posts/juliocasal_await-doesnt-create-a-new-thread-it-never-share-7444582351403151360-XWuH - What #dotNET #await does under the hood. Great tech breakdown https://www.linkedin.com/in/juliocasa.
await doesn't create a new thread. It never did. Here's what actually happens under the hood: 𝟏. 𝐓𝐡𝐞 𝐜𝐨𝐦𝐩𝐢𝐥𝐞𝐫 𝐫𝐞𝐰𝐫𝐢𝐭𝐞𝐬 𝐲𝐨𝐮𝐫 𝐦𝐞𝐭𝐡𝐨𝐝 → Your async method becomes a state… | Julio Casal | 31 comments
await doesn't create a new thread. It never did. Here's what actually happens under the hood: 𝟏. 𝐓𝐡𝐞 𝐜𝐨𝐦𝐩𝐢𝐥𝐞𝐫 𝐫𝐞𝐰𝐫𝐢𝐭𝐞𝐬 𝐲𝐨𝐮𝐫 𝐦𝐞𝐭𝐡𝐨𝐝 → Your async method becomes a state machine struct → Implements IAsyncStateMachine with a MoveNext() method → Each "await" becomes a pause point between states 𝟐. 𝐖𝐡𝐚𝐭 𝐡𝐚𝐩𝐩𝐞𝐧𝐬 𝐚𝐭 "𝐚𝐰𝐚𝐢𝐭" → The task is checked. If already completed, execution continues immediately. → If not, a continuation callback is registered → The current thread is released back to the thread pool → No thread is blocked. None. 𝟑. 𝐖𝐡𝐞𝐧 𝐭𝐡𝐞 𝐭𝐚𝐬𝐤 𝐜𝐨𝐦𝐩𝐥𝐞𝐭𝐞𝐬 → The continuation fires → MoveNext() is called again → The state machine picks up where it left off on a thread pool thread 𝟒. 𝐒𝐲𝐧𝐜𝐡𝐫𝐨𝐧𝐢𝐳𝐚𝐭𝐢𝐨𝐧𝐂𝐨𝐧𝐭𝐞𝐱𝐭 → ASP .NET Core: none. Continuations resume on any thread pool thread. → WPF/WinForms: captures the UI thread. This is where deadlocks happen. 𝟓. 𝐚𝐰𝐚𝐢𝐭 𝐝𝐨𝐞𝐬 𝐍𝐎𝐓 𝐜𝐫𝐞𝐚𝐭𝐞 𝐚 𝐧𝐞𝐰 𝐭𝐡𝐫𝐞𝐚𝐝 → It releases the current one. That's it. → This is the most common misconception about async in C#. 𝟑 𝐭𝐫𝐚𝐩𝐬 𝐭𝐡𝐚𝐭 𝐤𝐞𝐞𝐩 𝐬𝐡𝐨𝐰𝐢𝐧𝐠 𝐮𝐩: ❌ Calling .Result or .Wait() on a Task. Blocks the thread and risks deadlocks. ❌ Using async void (except for event handlers). Exceptions crash the process. ❌ Forgetting ConfigureAwait(false) in library code. Causes subtle context issues. I made a free .NET Interview Prep guide covering the questions senior devs actually get asked 👇 https://lnkd.in/g9bWNzkR | 31 comments on LinkedIn
The DAX continued its upward trend on Tuesday afternoon after a positive start to the trading day. Around 12:30 PM, the leading index was measured at approximat... https://news.osna.fm/?p=41827 | #news #amid #await #corporate #dax
