#programming #CSharp
Loop Optimizations in C# (and various other compilers)
This post comprises infographics showing various loop optimizations that happen in C# (dotnet) and other languages.
https://leveluppp.ghost.io/loop-optimizations-in-various-compilers/
Loop Optimizations in C# (and various other compilers)
This post comprises infographics showing various loop optimizations that happen in C# (dotnet) and other languages.
https://leveluppp.ghost.io/loop-optimizations-in-various-compilers/
#programming #CSharp
In recent years, there’s been a trend of strict null checking in programming languages:
* TypeScript has the strictNullChecks option.
* In Kotlin (preferred language for Android development), all types don’t allow null values by default.
* In Swift (Apple’s language of choice), only the Optional data type allows null values.
* Nullable reference types bring similar functionality to C#. The feature was originally planned for C# 7 and was finally released as part of C# 8.
In this tutorial, author looks at the state of the Nullable Reference Types feature in C#, one year after its initial release:
https://www.dotnetcurry.com/csharp/nullable-reference-types-csharp
In recent years, there’s been a trend of strict null checking in programming languages:
* TypeScript has the strictNullChecks option.
* In Kotlin (preferred language for Android development), all types don’t allow null values by default.
* In Swift (Apple’s language of choice), only the Optional data type allows null values.
* Nullable reference types bring similar functionality to C#. The feature was originally planned for C# 7 and was finally released as part of C# 8.
In this tutorial, author looks at the state of the Nullable Reference Types feature in C#, one year after its initial release:
https://www.dotnetcurry.com/csharp/nullable-reference-types-csharp
Dotnetcurry
Nullable Reference types in C# – Best practices | DotNetCurry
In this tutorial, I look at the state of the Nullable Reference Types feature in C#, one year after its initial release.
#programming #CSharp #debug
Diagnostics has always been a fundamental part of the .NET development experience. It enables developers to understand the runtime behavior of their programs, at both a high- and low-level. It’s also the set of tools that developers reach for to root-cause a failure and resolve it. The diagnostics team primarily builds low-level APIs that IDEs (like Visual Studio), Cloud Services (like Application Insights) or other systems use to provide end-user experiences. More recently, the team has been focused on command-line tools that provide end-user experiences of their own.
We’re using the conversation format again, this time with runtime engineers who work on diagnostics and related topics.
https://devblogs.microsoft.com/dotnet/conversation-about-diagnostics/
Diagnostics has always been a fundamental part of the .NET development experience. It enables developers to understand the runtime behavior of their programs, at both a high- and low-level. It’s also the set of tools that developers reach for to root-cause a failure and resolve it. The diagnostics team primarily builds low-level APIs that IDEs (like Visual Studio), Cloud Services (like Application Insights) or other systems use to provide end-user experiences. More recently, the team has been focused on command-line tools that provide end-user experiences of their own.
We’re using the conversation format again, this time with runtime engineers who work on diagnostics and related topics.
https://devblogs.microsoft.com/dotnet/conversation-about-diagnostics/
Microsoft News
Conversation about diagnostics
Conversation with .NET engineers about diagnostics, profiling and observability.