seteplia Archives | Premier Developer

The danger of TaskCompletionSource<T data-lazy-src=

class"/>

The danger of TaskCompletionSource class

Sergey TepliakovOctober 1, 2018Oct 1, 201810/1/18

... when used with async/await.
TaskCompletionSource class is a very useful facility if you want to control the lifetime of a task manually. I share a canonical example when TaskCompletionSource is used for converting the event-based asynchronous code to the Task-based pattern.

Combining iterator blocks and async methods in C#

Sergey TepliakovSeptember 5, 2018Sep 5, 201809/5/18

One of the best traits of a well-designed system is composability. Large systems are complex and hierarchical and one of the best ways to fight accidental complexity is to compose a system from smaller components. You write and test each component independently then you glue them together to achieve a higher-level behavior. Programming lang

Performance implications of default struct equality in C#

Sergey TepliakovJuly 17, 2018Jul 17, 201807/17/18

If you're familiar with C#, then you most likely heard that you should always override Equals and GetHashCode for custom structs for performance reasons. To better understand the importance and the rationale behind this advice we're going to look at the default behavior to see why and where the performance hit comes from. Then we'll look at a

Dissecting new generic constraints in C# 7.3

Sergey TepliakovJune 12, 2018Jun 12, 201806/12/18

During the last Build conference, Microsoft has announced the next version of Visual Studio with C# 7.3 support. This is yet another minor language update with some quite interesting features. The main change was related to generics, starting from C# 7.3 there 3 more constraints: unmanaged, System.Enum and System.Delegate. The unmanaged const

Avoiding struct and readonly reference performance pitfalls with ErrorProne.NET

Sergey TepliakovMay 3, 2018May 3, 201805/3/18

As you may know from my previous posts "The 'in'-modifier and the readonly structs in C#" and "Performance traps of ref locals and ref returns in C#", structs are trickier then you might think. Mutability aside, the behavior of readonly and non-readonly structs in "readonly" contexts is very different. Structs are meant for high-performance

Performance traps of ref locals and ref returns in C#

Sergey TepliakovApril 11, 2018Apr 11, 201804/11/18

The C# language from the very first version supported passing arguments by value or by reference. But before C# 7 the C# compiler supported only one way of returning a value from a method (or a property) - returning by value. This has been changed in C# 7 with two new features: ref returns and ref locals. But unlike other features that were

Nullable types arithmetic and null-coalescing operator precedence

Sergey TepliakovMarch 30, 2018Mar 30, 201803/30/18

Here is a simple question for you: which version of a GetHashCode() is correct and what performance impact does the incorrect version have?

The ‘in’-modifier and the readonly structs in C#

Sergey TepliakovMarch 7, 2018Mar 7, 201803/7/18

C# 7.2 got two very important features for high-performance scenarios -- the readonly structs and the in parameters. But to understand why this additions are so important and how they're related to each other we should look back in history. As you probably know, the .NET ecosystem has two family of types -- the value types (a.k.a. structs)

One user scenario to rule them all

Sergey TepliakovFebruary 14, 2018Feb 14, 201802/14/18

The async series Almost every non-trivial behavior of the async methods in C# can be explained based on one user scenario: migration of the existing synchronous code to asynchronous should be as simple as possible. You should be able to add async keyword before a method's return type, add Async suffix to its name, add awai

The performance characteristics of async methods in C#

Sergey TepliakovJanuary 25, 2018Jan 25, 201801/25/18

The async series In the last two blog posts we've covered the internals of async methods in C# and then we looked at the extensibility points the C# compiler provides to adjust the behavior of async methods. Today we're going to explore the performance characteristics of async methods. As you should already know from th

Premier Developer