Imagine we have a simple class, a wrapper around some array of structs (better data locality etc.) ...

Nie przekacuj parametrów w ten sposób w Entity Framework Core 5 Niedawno napisałem post o wykonywaniu poleceń SQL w Entity Framework Core 5: Wykonanie polecenia SQL w Entity Framework Core 5. Jeden z czytelników zauważył, że popełniłem duży błąd podczas przekazywania parametrów. Przyjrzyjmy się bliżej.

This is video is the start of a brand new series of videos about C# / CLR internals. We're going to look at C# Switch Case Internals and what interesting things happen under the hood and how well it performs as compared to if-else statements.

Tym razem chciałbym się skupić na tym, jak dostarczyć odpowiednie fragmenty kodu klienta API do pozostałych członków zespołu tak, by każdy mógł go używać w odpowiedni sposób.

Pierwszy techniczny artykuł w Cesarstwie-Dev, i od razu coś ekstra! Połączenie dwóch tematów, które są bardzo bliskie memu sercu – integracje z zewnętrznymi systemami oraz testy! To co? Zaczynajmy!

In this video, we're going look at struct devirtualization and how this feature works in the runtime today. We're going to look at some ways we can (ab)use this feature and what are the problems with the current implementation.

In this video, we're going look in what situations JIT will emit bounds check for arrays and how to force it to generate bounds-check free code. Bounds Check elimination is something that we want to do to increase performance since each check has a cost associated with it especially that it will emit a possible branch. ♦ link to loop clone video: https://youtu.be/zxcHkEu6aTY

In this video, we're going look at how JIT folds constants and optimizes functions buy inlining and then folding them. We shall also see a couple of examples where the compiler will refuse to fold code that would seem to be easy to fold. Note: At (8:30) I've made an editing error and the music gets very loud for ~10s and then it goes back down to normal volume, sorry about that. ♦ link to shift trick video: https://youtu.be/VxiZ7tV-XkM

The IEEE 754 specification defines many floating point types, including: binary16, binary32, binary64 and binary128. Most developers are familiar with binary32 (equivalent to float in C#) and binary64 (equivalent to double in C#). They provide a standard format to represent a wide range of values with a precision acceptable for many applications. .NET has always had float and double and with .NET 5 Preview 7, we’ve added a new Half type (equivalent to binary16)!

This video is the start of a brand-new video series about JIT compilation in C# called: "What the JIT". This time we're going to look at simple integer arithmetic like division and multiplication and how JIT is able to optimize that.