One of this year’s most anticipated developments is C# 9, which will rejoice the programmer community with new, exciting features. Even though there are no concrete facts or declarations about which features will be incorporated in the final release, we can already talk about the most popular proposals based on this GitHub list of Language Version Planning for C# and the feature ideas suggested by the community.
In this article, we are going to introduce and detail the 5 most anticipated features of C# 9, which are the following:
Let’s explore them one by one!
Writing countless null checks can be tedious. Moreover, building lines of if statements with nested exceptions are not at all aesthetic. However, the simplified null validation proposal would allow coders to eliminate the need for explicit null checking by adding the “!” operator to the parameter, which will trigger the C# compiler to give off a standard “null” checking code. This feature would potentially make the argument validation visible to upstream callers via IntelliSense. Read more details about this code enhancement proposal.
Another handy proposal, which has been the topic of discussions since the release of C# 6, is the idea of primary constructions. This feature would allow programmers to make class constructions simpler just like in TypeScript, Kotlin, and other languages. Primary constructions would aim to reduce the overhead by putting constructor arguments directly in scope throughout the class.
Code without Primary constructions:
Code with primary constructions:
This method would result in a significantly shorter code, which also decreases the possibility of code-breaks and errors, as the code you don’t have to write won’t break. Furthermore, by eliminating redundant boilerplate code developers would be able to make their code files easier to skim through. Not to mention that these solutions ease their job when it comes to uncovering bugs.
The new CallerArgumentExpression feature would come to your help in C# 9 when an assertion or an argument validation fails. When something like this happens, all coders want to know in as many details as possible where and why it occurred. However, in the current stack trace, with the use of Debug info in the code, it is only the file name, the line number, and the method number that is given to them, which is most of the time not enough to tell the assert that failed.
This is why the C# community proposed the CallerArgumentExpression to be included in the new C# 9 release. This would allow the caller to project the expressions passed in at a call site as a string. When using this solution, the constructor of the attribute will need to pick a string argument that specifies the name of the argument in order to project it as a string, in other words, to stringify it.
Developers could add the CallerArgumentExpression to Debug.Assert as follows, to get the requested information:
One of the proposals of C# 9 would give a new, focused and time-saving usage for the word “new”. In the case of new type-targeted expressions, where you already know the type, you could totally forget about the type specifications for constructions. Since the type of expressions is already known, this new “New” would allow you to simplify their usage by entering “new()” instead of “new Dictionary<string, list<string="">>()”.</string,>
“Enum class”-es are a new kind of type declarations. They are usually referred to as Discriminated Unions, due to the fact that they list every single instance type, while the instances do not overlap with each other. To put it differently, discriminated unions are a great solution to define types that encompass any number of dissimilar data types. They are used to enumerate different values.
At the moment C# does not fully support discriminated unions, only via inheritance and some extent of overloading, though having concise and seamless support for these declarations should undoubtedly exist in this programming language, according to the majority of C# developers.
All things considered, it looks like C# gains its popularity by adapting to the requirements of developers and by making learning and adaptation easier for those programmers, who do not specialize in a single programming language. The 5 new feature proposals mentioned above clearly show the way how C# intends to support more functional programming techniques. These improvements make the life of developers easier, while they increase the number of the programming language’s fanbase.
Please note that the above-mentioned features are not guaranteed to be part of the new C# 9 release, though it is great to be on top of IT news and follow the course of the development.
It has not been revealed when the release will roll out. One thing's for sure, though: a major Visual Studio update will be needed for it.
Sitecore JSS and Sitecore Headless is out for a few years now but we started our first headless project last year. Our chosen stack was Sitecore Headless 10.2 with Next.js SDK (19.0.0) using Server-Side Rendering (SSR). I would like to talk about 2 main topics in this post. The first one is how the development processes are changed because of the changed tech stack. The second part is about the technical challenges we met during the implementation.
Workforce diversity is necessary for business. Teams made up of people with greater individual differences between each other leads to higher productivity and better performance. Despite statistics showing how GDP will increase by an average of 35%with a closed gender pay gap, women in tech remain at a disadvantage over men. Where women take up less than 10% of C-Suite positionsat tech firms, there’s plenty of room to promote representation, leadership and inclusion of women at all levels –from CTO to administrator. And when it is, there is no doubt that a more motivated and higher-performing workforce will emerge.
Agile software development is pretty popular nowadays, but it can be frustrating for people in various roles working on the project. Here are a couple of notes on the experience that we faced on recent projects.
Imagine that you’re a software development company that started to work with British and North American companies a long time ago, preferring AWS as their cloud provider. So, you have already picked up a significant amount of knowledge and experience about AWS. Then, some of your clients’ recent developments required some Azure and Microsoft API-related knowledge as well to achieve their goals. Let’s review our two recent case studies where having a partner experienced in Azure turned out to be beneficial and efficient for our client.