الوعود والمستقبلات والعمليات غير المتزامنة
استكشف أنماط البرمجة غير المتزامنة في Clojure للتعامل مع المهام طويلة التشغيل وعمليات الإدخال والإخراج غير الحاجبة
الوعود والمستقبلات والعمليات غير المتزامنة درس مجاني في Clojure Functional Programming & JVM Backend Development على CoddyKit. هذا هو الدرس 3 من أصل 4. يمكنك قراءة الدرس كاملاً أدناه مجاناً — ثم تمرن عليه مباشرة في المتصفح باستخدام محرر أكواد مدمج ومدرس ذكاء اصطناعي متاح 24/7. هذا الدرس جزء من مسار التعلم في Clojure Functional Programming & JVM Backend Development، وتقدمك يتزامن عبر الويب وتطبيق CoddyKit. تتضمن دورة Clojure Functional Programming & JVM Backend Development 4 دروس في المجموع.
بعض أجزاء هذا الدرس لم تُترجم بعد وتظهر باللغة الإنجليزية.
Intro to Asynchronous Programming
Welcome! In this lesson, we'll explore asynchronous programming in Clojure. This is key for building responsive applications that don't freeze while waiting for long tasks.
Asynchronous tasks run in the 'background', allowing your main program to continue without interruption. When the background task finishes, it delivers its result.
Blocking vs. Non-Blocking
Imagine fetching data from a slow server. A blocking operation would make your application wait until the data arrives. During this time, nothing else can happen.
A non-blocking operation starts the fetch but immediately returns control to your application. Your app can then do other things, and process the data once it's available.
Clojure's 'future' Macro
Clojure provides the future macro to run a computation on a separate thread. This makes the computation asynchronous and non-blocking from the caller's perspective.
The future immediately returns a 'future' object, which is a placeholder for the eventual result.
Using 'future' for Async Tasks
Let's see future in action. We'll simulate a long-running task using Thread/sleep. Notice how the "Future started" message appears instantly.
(ns my-app.core
(:gen-class))
(defn -main
"Demonstrates a simple future."
[& args]
(println "Main thread: Starting future...")
(let [f (future
(println " Future thread: Working...")
(Thread/sleep 2000) ; Simulate work
(println " Future thread: Done!")
"Result from Future")]
(println "Main thread: Future started, continuing...")
; We'll learn how to get the result next!
(Thread/sleep 1000) ; Let main thread do other work
(println "Main thread: End of main.")))Getting Results from 'future'
To get the actual value from a future, you dereference it. You can use the @ reader macro or the deref function.
If the future's computation isn't finished yet, dereferencing will block the current thread until the result is ready.
(ns my-app.core
(:gen-class))
(defn -main
"Dereferencing a future."
[& args]
(println "Main thread: Starting future...")
(let [f (future
(println " Future thread: Working...")
(Thread/sleep 2000)
"Long Task Complete")]
(println "Main thread: Future launched.")
(println "Main thread: Doing other work...")
(Thread/sleep 500)
(println "Main thread: Now waiting for future result...")
(let [result @f] ; Dereference the future
(println "Main thread: Future result:" result))
(println "Main thread: All done!")))Clojure's 'promise' Function
While future runs a computation, a promise is a placeholder for a value that will be delivered later, usually by another thread or an external event.
Think of it as an empty box that someone else will fill. You can wait for the box to be filled by dereferencing it.
Delivering and Dereferencing a Promise
The deliver function is used to put a value into a promise. Once a promise is delivered, its value cannot be changed.
Dereferencing a promise works just like a future: it will block until a value is delivered.
(ns my-app.core
(:gen-class))
(defn -main
"Delivering and dereferencing a promise."
[& args]
(let [p (promise)]
(println "Main thread: Created a promise.")
(future
(println " Future thread: Doing async work...")
(Thread/sleep 1500)
(let [val "Value from Future!"]
(println " Future thread: Delivering value to promise.")
(deliver p val)))
(println "Main thread: Waiting for promise to be delivered...")
(let [result @p] ; Blocks until 'deliver' is called
(println "Main thread: Promise received:" result))
(println "Main thread: Program finished.")))Future and Promise Together
future and promise often work together. A future might perform a complex calculation, and then deliver its result to a promise, which can then be picked up by another part of your application.
This pattern is useful for coordinating between different asynchronous tasks or threads.
(ns my-app.core
(:gen-class))
(defn long-calculation []
(println " Calculation: Starting...")
(Thread/sleep 2500) ; Simulate heavy work
(println " Calculation: Finished.")
(* 123 456))
(defn -main
"Coordinating with future and promise."
[& args]
(let [calc-promise (promise)]
(println "Main: Kicking off calculation...")
(future ; Run calculation in a separate thread
(let [result (long-calculation)]
(deliver calc-promise result)))
(println "Main: Calculation started. Doing other things...")
(Thread/sleep 1000)
(println "Main: Still doing other things...")
(println "Main: Waiting for calculation result...")
(let [final-result @calc-promise]
(println "Main: Received final result:" final-result))
(println "Main: Done.")))Error Handling with Async Tasks
When an exception occurs inside a future or before a promise is delivered, dereferencing the future/promise will re-throw that exception on the dereferencing thread.
This allows you to handle errors in your main thread, even if they originate from an asynchronous task.
Quick Check: Async Behavior
Consider the following Clojure code snippet:
(let [f (future (Thread/sleep 1000) "Async Result")]
(println "Started")
(Thread/sleep 500)
(println "Waiting...")
(let [result @f]
(println "Got:" result)))
What is the *minimum* total time before "Got: Async Result" is printed?
Recap: Promises, Futures & Async
- Asynchronous programming allows tasks to run without blocking the main program flow.
- Clojure's
futuremacro runs a computation on a separate thread, returning a placeholder immediately. - The
promisefunction creates a placeholder that can bedelivered a value later, often from another thread or external source. - Both
futureandpromiseare dereferenced (using@orderef) to retrieve their values, blocking if the value isn't ready. - Exceptions in async tasks are re-thrown when dereferenced.
الأسئلة الشائعة
هل درس «الوعود والمستقبلات والعمليات غير المتزامنة» مجاني؟
نعم — نص درس «الوعود والمستقبلات والعمليات غير المتزامنة» كامل متاح مجاناً هنا على الويب. لتمرينه بشكل تفاعلي (محرر أكواد مدمج ومدرس ذكاء اصطناعي متاح 24/7) وفتح باقي دورة Clojure Functional Programming & JVM Backend Development، انتقل إلى CoddyKit PRO. تتضمن دورة Clojure Functional Programming & JVM Backend Development 4 دروس في المجموع.
ماذا ستتعلم في «الوعود والمستقبلات والعمليات غير المتزامنة»؟
استكشف أنماط البرمجة غير المتزامنة في Clojure للتعامل مع المهام طويلة التشغيل وعمليات الإدخال والإخراج غير الحاجبة تتمرن على Clojure Functional Programming & JVM Backend Development مع أكواد عملية تشغلها مباشرة في المتصفح، ومدرس ذكاء اصطناعي متاح 24/7 يجيب على أسئلتك أثناء عملك.
هل أحتاج إلى خبرة سابقة لأبدأ Clojure Functional Programming & JVM Backend Development؟
لا تُشترط خبرة سابقة. Clojure Functional Programming & JVM Backend Development على CoddyKit منظم للمبتدئين حتى المتقدمين، لذا يمكنك البدء من هنا أو من البداية والتقدم بسرعتك الخاصة. هذا هو الدرس 3 من أصل 4.
كم من الوقت يستغرق درس «الوعود والمستقبلات والعمليات غير المتزامنة»؟
معظم دروس CoddyKit تستغرق حوالي 5–10 دقائق. كل منها موجز وتفاعلي، لذا تحرز تقدماً مستمراً وتستأنف من حيث توقفت عبر الويب والتطبيق.
هل يمكنني كتابة وتشغيل أكواد في درس Clojure Functional Programming & JVM Backend Development هذا؟
نعم. كل درس في Clojure Functional Programming & JVM Backend Development يتضمن محرر أكواد مدمج، لذا تكتب وتشغل أكواداً حقيقية مباشرة في متصفحك وتحصل على تعليقات فورية من الذكاء الاصطناعي — بدون إعداد محلي.
جميع الدروس في هذه الدورة
- Refs وAgents وAtoms لإدارة الحالة
- الذاكرة المعاملاتية للبرمجيات (STM)
- الوعود والمستقبلات والعمليات غير المتزامنة
- قنوات core.async وكتل Go