#it3xl

The pattern has a unsafe context switching. It can make you pain. Look at JSFiddle Revealing Prototype Pattern error prone point Think twice before use it. Revealing Module Pattern is cool (and  FFE ).

Async execution - It's all about responsiveness. Old code scenarios To use WaitHandle from a Task. Implement the APM pattern by FromAsync methods and "Tasks Forest" Implement the EPM pattern by TaskCompletionSource. Asynchronous Task means the Threadless Task. Asynchronous Tasks may have only the next statuses: Fault, RunToCompletion, Cancelled. Continuation for Asynchronous Tasks Use the TaskCompletionSource<T> class. async await A syntactic sugar for awful amount of work. A compiler's underground job. A enumeration, try, finally, using and etc. Users SynchronizationContext implicitly. Unwrap multiple exceptions The await will return only the first exception from a AggregateException. There is a useful trick to unwrap multiple exceptions. await task.ContinueWith(     ( ) => { } ,     TaskContinuationOptions. ExecuteSynchronously ); var results = task .Result; Multiple await Preventing of lost exceptions wit...

Asynchronous Programming Parallel Programming Multithreaded Programming

Parallel execution - It's all about loaded computations. Common Types of Parallelism Data     amount of data processed by one operation in parallel. Patterns     Parallel Loops Implementations     Parallel.Foreach     Parallel.For Task     Some data or amount of data processed by many operations. Patterns     Parallel tasks Implementations     Parallel.Invoke Dataflow     Operations processed in some flow or order. Patterns     Features     Pipeline Embarrassingly parallel     computations entirely independent of one another. No dataflow in between the options. Patterns Parallel Loops Parallel.For / Parallel.Foreach Parallel Tasks Parallel.Invoke Parallel Aggregation Map- Reduce Producer-Consumer By Parallel Loops with TLS (Task Local Storage) parameter or by Wait All One By One Futures Dynamic Task Parallelism Pipelines + Concurrent D...

Synchronization primitives Semaphore Slim

IAsyncResult needs to be closed.

Key objects must be immutable as long as they are used as keys in the Hashtable. When an element is added to the Hashtable, the element is placed into a bucket based on the hash code of the key. Subsequent lookups of the key use the hash code of the key to search in only one particular bucket, thus substantially reducing the number of key comparisons required to find an element. GetBucket(item. GetHashCode ()) Any object that creates a hashvalue should change the hashvalue, when the object changes, but it must not - absolutely must not - allow any changes to itself, when it is used inside a Hashtable (or any other Hash-using object, of course). So, just make GetHashCode result change, when the object data changes, and if the use of the object inside of hash using lists or objects is intended (or just possible) then make the object either immutable or create a readonly flag to use for the lifetime of a hashed list containing the object. (By the way: All of this is not C# oder...