Add quick reference section and validate disposal patterns work

Co-authored-by: thomhurst <30480171+thomhurst@users.noreply.github.com>

Author: Copilot

EnumerableAsyncProcessor.Example/DisposalExample.cs

@@ -12,6 +12,12 @@ namespace EnumerableAsyncProcessor.Example;
 /// <summary>
 /// Examples demonstrating proper disposal patterns for EnumerableAsyncProcessor objects.
 /// This addresses the common question: "How/when to correctly dispose the resulting processor objects?"
+/// 
+/// QUICK ANSWER: Always dispose processor objects using 'await using' or manual disposal!
+/// 
+/// The key pattern is:
+/// ❌ BAD:  var processor = items.SelectAsync(...).ProcessInParallel(); // Never disposed!
+/// ✅ GOOD: await using var processor = items.SelectAsync(...).ProcessInParallel(); // Auto-disposed!
 /// </summary>
 public static class DisposalExample
 {

README.md

@@ -390,3 +390,36 @@ var transformedResults = await asyncEnumerable.ProcessInParallel(async x => awai
 ```
 
 The disposal guidance above applies when you're working with the processor objects directly (using the builder pattern).
+
+## Quick Reference: Disposal Patterns
+
+### ❌ INCORRECT (Resource Leak)
+```csharp
+// DON'T DO THIS - Never disposed!
+var processor = input.SelectAsync(transform, token).ProcessInParallel();
+return processor.GetResultsAsyncEnumerable();
+```
+
+### ✅ CORRECT Patterns
+
+#### Option 1: Await Using (Recommended)
+```csharp
+await using var processor = input.SelectAsync(transform, token).ProcessInParallel();
+return await processor.GetResultsAsync();
+```
+
+#### Option 2: Manual Disposal
+```csharp
+var processor = input.SelectAsync(transform, token).ProcessInParallel();
+try {
+    return await processor.GetResultsAsync();
+} finally {
+    await processor.DisposeAsync();
+}
+```
+
+#### Option 3: Extension Methods (Auto-Disposal)
+```csharp
+// These handle disposal internally
+var results = await asyncEnumerable.ProcessInParallel(transform);
+```