{"id":28816,"date":"2020-02-19T23:45:00","date_gmt":"2020-02-19T22:45:00","guid":{"rendered":"https:\/\/blexin.com\/le-novita-di-c-8-seconda-parte\/"},"modified":"2021-05-20T18:40:37","modified_gmt":"2021-05-20T16:40:37","slug":"new-features-of-c-8-part-two","status":"publish","type":"post","link":"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/","title":{"rendered":"New features of C# 8: part two"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

In my previous article, we discover the first part of the new features of C#8: let\u2019s see now together what else this new version of Microsoft\u2019s home language makes available to us.<\/p>\n\n\n\n

New Switch Expression<\/strong><\/h2>\n\n\n\n

The new switch expressions have been released, and they introduce a compact method for writing switch\/case expressions.
I show you with an example of what I am talking about:<\/p>\n\n\n

\npublic static string GetWaterCondition(WaterCondition condition) =>\ncondition.Sea switch\n{\n\u00a0\u00a0\u00a0\u00a0Sea.Calm => "The sea is calm",\n\u00a0\u00a0\u00a0\u00a0Sea.Rough => "The sea is rough",\n\u00a0\u00a0\u00a0\u00a0Sea.VRough => "The sea is very rough",\n\u00a0\u00a0\u00a0\u00a0_ => "Undefined"\n};\n<\/pre><\/div>\n\n\n
As you can note:<\/p>\n\n\n\n
  • the variable foreruns the keyword switch<\/em> <\/li>
  • The \u201c=>\u201d substitutes the elements \u201ccase\u201d and \u201c:\u201d<\/li>
  • An underscore (or discard) \u201c_\u201d substitutes the default case<\/li>
  • Bodies are expressions and not instructions <\/li><\/ul>\n\n\n\n
    Properties criteria<\/strong><\/h2>\n\n\n\n
    Thanks to the previous syntax, we can use the property matching too. We can indicate properties themselves in the conditions, instead of specifying the object to evaluate:<\/p>\n\n\n
    \npublic static string GetWaterCondition(WaterCondition condition) => condition switch\n{\n\u00a0\u00a0\u00a0\u00a0{Sea: Sea.Calm} => "The sea is calm",\n\u00a0\u00a0\u00a0\u00a0{Sea: Sea.Rough} => "The sea is rough",\n\u00a0\u00a0\u00a0\u00a0{Sea: Sea.VRough, Wind: Wind.Strong} => "There\u2019s a storm!",\n\u00a0\u00a0\u00a0\u00a0{Sea: Sea.VRough} => "The sea is very rough",\n\u00a0\u00a0\u00a0\u00a0null => \u201cUnknown\u201d,\n\u00a0\u00a0\u00a0\u00a0_ => "Undefined"\n};\n<\/pre><\/div>\n\n\n
    We evaluate the property Sea<\/em> as before, but we can evaluate the property Wind<\/em> too, and, in addition to the default value (\u201c_\u201d), we can check if the value is null too.Please pay attention to the evaluation order: in the previous code snippet, we need to evaluate the much specific condition with a very rough sea and strong wind<\/em> (There\u2019s a storm!<\/code>) and then pass to the condition of a very rough sea<\/em> (The sea is very rough<\/code>).<\/p>\n\n\n\n
    Criteria for tuples<\/strong><\/h2>\n\n\n\n
    It is possible to use the tuple <\/em>(tuple pattern<\/em>), which are similar to the property pattern, as switch<\/em> argument:<\/p>\n\n\n
    \npublic string Location(string country, string city)\n\u00a0\u00a0\u00a0=> (country, city) switch\n\u00a0\u00a0\u00a0{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0("IT", "Naples") => "Naples, Italy (Campania)\u201d,\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0(_, "Naples") => "Italy (Campania),\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0United States (Utah),\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0United States (Texas),\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0United States (Florida),\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0United States (New York)",\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0("IT", _) => "Italy",\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0_ => "Not Found", \/\/Short form for ( _, _) => "Not Found"\n\u00a0\u00a0\u00a0};\n<\/pre><\/div>\n\n\n
    Positioning criteria<\/strong><\/h2>\n\n\n\n
    Some objects directly or indirectly implement the deconstruct<\/em> introduced with C#7, that \u201csmooths over\u201d an object in a parameters list.
    Using the deconstruct<\/em> and the when<\/em> clause in a switch<\/em> instruction, we can use the positional pattern<\/em>. In this example, we can see how easy it is to map a point in a Cartesian plane to see in which quadrant it is placed.
    Supposing, we have this type of implementation:<\/p>\n\n\n
    \npublic class Point\n{\n\u00a0\u00a0\u00a0\u00a0public int X { get; }\n\u00a0\u00a0\u00a0\u00a0public int Y { get; }\n\u00a0\n\u00a0\u00a0\u00a0\u00a0public Point(int x, int y) => (X, Y) = (x, y);\n\u00a0\n\u00a0\u00a0\u00a0\u00a0public void Deconstruct(out int x, out int y) => (x, y) = (X, Y);\n}\n<\/pre><\/div>\n\n\n
    The object Point is deconstructed and inserted in a tuple; then we use the then clause to determine in which quadrant is the point:<\/p>\n\n\n
    \nprivate string GetPointPosition(Point point) => point switch\n{\n\u00a0\u00a0\u00a0\u00a0(0, 0) => "origin",\n\u00a0\u00a0\u00a0\u00a0var (x, y) when x > 0 && y > 0 => "dx-up",\n\u00a0\u00a0\u00a0\u00a0var (x, y) when x < 0 && y > 0 => "sx-up",\n\u00a0\u00a0\u00a0\u00a0var (x, y) when x < 0 && y < 0 => "sx-down",\n\u00a0\u00a0\u00a0\u00a0var (x, y) when x > 0 && y < 0 => "dx-down",\n\u00a0\u00a0\u00a0\u00a0var (_, _) => "on border",\n\u00a0\u00a0\u00a0\u00a0_ => "unknown"\n};\n<\/pre><\/div>\n\n\n
    Index and intervals<\/strong><\/h2>\n\n\n\n
    Two new types <\/em>have been introduced:<\/p>\n\n\n\n
    • System.Index<\/em> that represents an index in a sequence<\/li>
    • System.Range<\/em> that represents a secondary interval in a sequence<\/li><\/ul>\n\n\n\n
      There have been introduced two new operators too:<\/p>\n\n\n\n
      • the operator \u201c^\u201d<\/em>, which specifies that an index starts from the end of the sequence<\/li>
      • the interval operator \u201c..<\/em>\u201d, which specifies the beginning and the end of an interval as operand<\/li><\/ul>\n\n\n\n
        Let\u2019s try to understand, using a daysOfWeek <\/em>matrix:<\/p>\n\n\n
        \nvar daysOfWeek = new string[]\n{\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\/\/ Index from start\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Index from end\n\u00a0\u00a0\u00a0\u00a0"Monday",\u00a0\u00a0\u00a0\u00a0 \/\/ 0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ^7\n\u00a0\u00a0\u00a0\u00a0"Tuesday",\u00a0\u00a0\u00a0 \/\/ 1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ^6 \n\u00a0\u00a0\u00a0\u00a0"Wednesday",\u00a0 \/\/ 2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ^5\n\u00a0\u00a0\u00a0\u00a0"Thursday",\u00a0\u00a0 \/\/ 3\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ^4\n\u00a0\u00a0\u00a0\u00a0"Friday",\u00a0\u00a0\u00a0\u00a0 \/\/ 4\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ^3\n\u00a0\u00a0\u00a0\u00a0"Saturday",\u00a0\u00a0 \/\/ 5\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ^2\n\u00a0\u00a0\u00a0\u00a0"Sunday"\u00a0\u00a0\u00a0\u00a0\u00a0 \/\/ 6\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ^1\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\/\/ 7 (or daysOfWeek.Length) ^0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \n};\n<\/pre><\/div>\n\n\n
        Index [0] is equal to index [^7] , \u201cMonday\u201d in this case.
        Index [7] is equal to index [^0], that is daysOfWeek[daysOfWeek.Length], and then they would generate an exception. For any n number, index ^n is equal to daysOfWeek.Length – n.<\/p>\n\n\n\n
        An interval (\u201c..\u201d) specifies the beginning and the end of an interval. The beginning of the interval is inclusive, but the end is not included in the interval.
        We, therefore, have several options to obtain specific intervals:<\/p>\n\n\n
        \nvar allDays = daysOfWeek[..]; \/\/Contains all the days of week\nvar startOfTheWeek = daysOfWeek[..2]; \/\/ "Monday", "Tuesday"\nvar weekend = daysOfWeek[5..]; \/\/ "Saturday", "Sunday"\nvar someDays = daysOfWeek[^5..^3]; \/\/ "Wednesday", "Thursday"\n<\/pre><\/div>\n\n\n
        The two new types, Index <\/em>and Range<\/em>, can be created through the respective constructors, or through a shortcut of C# 8, as in the following example:<\/p>\n\n\n
        \n\/\/ daysOfWeek[0]\nIndex monday = 0;\n\u00a0\n\/\/ "Wednesday", "Thursday"\nRange someDays = 2..4;\n<\/pre><\/div>\n\n\n
        The interval can then be used as a variable:<\/p>\n\n\n
        \nvar days = daysOfWeek[someDays];\n<\/pre><\/div>\n\n\n
        Nullable reference types<\/strong><\/h2>\n\n\n\n
        As we know, an object can be of a value type, belonging to primitive types such as numbers, struct, etc.
        They reside in a memory zone called stack and always have a value, even if they are a predefined constant. The reference types, like all the classes and the strings, have to be instantiated in a managed heap and their reference maintained through one variable. This last can assume a null value. To have a null variable means to point at any object.<\/p>\n\n\n\n
        One of the features added in C# 8, that got more prominence, was the introduction of the new Nullable<\/em> flag, which one, if added directly in the file with an extension. csproj, can enable or disable nullable annotation context<\/em> and nullable warning context<\/em>. Valid options are the following:<\/p>\n\n\n\n
        • enable <\/strong>– The nullable annotation contex<\/em>t and the nullable warning context<\/em> are enabled: variables of a reference type are non-nullable. All Null support warnings are enabled.<\/li>
        • warnings<\/strong> – The nullable annotation context <\/em>is disabled, while the nullable warning context <\/em>is enabled: variables of a reference type are independent of values. All null <\/em>support warnings are enabled.<\/li>
        • annotations<\/strong> – The nullable annotation context <\/em>is enabled, while the nullable warning context i<\/em>s disabled: variables of a reference type do not allow null<\/em> values. All null<\/em> support warnings are disabled.<\/li>
        • disable<\/strong> – The nullable annotation context <\/em>and nullable warning context<\/em> are disabled: variables of a reference type are independent of values, as in previous C# versions. All null <\/em>support warnings are disabled.<\/li><\/ul>\n\n\n
          \n<Nullable>enable<\/Nullable>\n<\/pre><\/div>\n\n\n
          We are stating that the compiler must check how we use and how we assign any kind of reference.
          Within a context of nullable annotations<\/em>, any variable of a reference type is considered as a non-nullable reference type. If you want to indicate that a variable can be null<\/em>, you need to add \u201c?\u201d to the name of the type to declare the variable as a nullable reference type.<\/p>\n\n\n
          \nstring? name;\n<\/pre><\/div>\n\n\n
          For non-nullable reference types, the compiler uses the flow analysis to ensure that local variables are initialized to a value other than null<\/em> at the time of declaration. Fields must be initialized during construction. A variable must be set by one of the available constructors or by an initializer to a value other than null.<\/em> Moreover, a value that could be null<\/em> cannot be assigned to the reference types.<\/p>\n\n\n\n
          The nullable reference types are not checked to see if they are assigned or initialized to null<\/em>. However, the compiler uses flow analysis to ensure that any variable of a nullable reference type is checked for null <\/em>values before access or before it is assigned to a non-nullable reference type.<\/p>\n\n\n\n
          In essence, if the feature is activated, objects not explicitly declared as Nullable<\/em> will generate a warning in the compilation, if they are set, or there is the possibility that they can assume a null value.<\/p>\n\n\n\n
          You can tell the compiler that we are sure that a variable (e.g.: name<\/em>), can\u2019t be null, and then avoid checking it, using the operator\u201c!\u201d.<\/p>\n\n\n
          \nname!.Length;\n<\/pre><\/div>\n\n\n
          You can also use directives to set these same contexts anywhere in the project, not only for individual files but also anywhere within a class:<\/p>\n\n\n\n
          • #nullable enable<\/code>:sets nullable annotation context and nullable alarm context on enabled<\/strong>.<\/li>
          • #nullable disable<\/code>: sets nullable annotation context and nullable alarm context on disabled<\/strong>.<\/li>
          • #nullable restore<\/code>: restores nullable annotation context and nullable alarm context in the project settings.<\/li>
          • #nullable disable warnings<\/code>: sets the nullable alarm context on disabled<\/strong>.<\/li>
          • #nullable enable warnings<\/code>: sets nullable alarm context on enabled<\/strong>.<\/li>
          • #nullable restore warnings<\/code>: restores the nullable alarm context in the project settings.<\/li>
          • #nullable disable annotations<\/code>: :sets nullable annotation context on disabled<\/strong>.<\/li>
          • #nullable enable annotations<\/code>: :sets nullable annotation context on enabled<\/strong>.<\/li>
          • #nullable restore annotations<\/code>: restores the annotation warning context in the project settings.<\/li><\/ul>\n\n\n\n
            By default, annotation and nullable warning contexts are disabled<\/strong>. The existing code is then compiled without modification and without generating new warnings.
            There are many control rules, and I don\u2019t want to go any further. If you are curious about the subject, check the official documentation.<\/p>\n\n\n\n
            Null-coalescing assignment<\/strong><\/h2>\n\n\n\n
            The join assignment operator null \u201c?=\u201d was also introduced.<\/p>\n\n\n\n
            You can use the operator \u201c?=\u201d to assign the value of the right operand of an assignment to the left operand only if the left operand returns null.<\/p>\n\n\n
            \nList<int> numbers = null;\nnumbers ??= new List<int>();\n<\/pre><\/div>\n\n\n
            Stackalloc in nested expressions<\/strong><\/h2>\n\n\n\n
            The stackalloc<\/em> operator allocates a memory block in the stack<\/em>. A memory block allocated to the stack<\/em>, created during the execution of the method, is automatically deleted when the method is returned.<\/p>\n\n\n\n
            With C# 8, if the result of a stackalloc<\/em> expression is System.Span<T><\/em> or System.ReadOnlySpan<T><\/em>, you can use the stackalloc<\/em> expression in other expressions:<\/p>\n\n\n
            \nSpan<int> numbers = stackalloc[] { 1, 2, 3, 4, 5, 6 };\nvar indx = numbers.IndexOfAny(stackalloc[] { 2, 4, 6 ,8 });\nConsole.WriteLine(indx);\u00a0 \/\/ output: 1\n<\/pre><\/div>\n\n\n
            Improvement of interpolated verbatim strings<\/strong><\/h2>\n\n\n\n
            Until now, the order of the interpolated string tokens required the token \u201c$\u201d to precede the token \u201c@\u201d.
            Now, the order of the two tokens is indifferent.<\/p>\n\n\n\n
            The strings:<\/p>\n\n\n
            \n$@"..."\n@$"..."\n<\/pre><\/div>\n\n\n
            are both valid interpolated strings.<\/p>\n\n\n\n
            We conclude our journey to the discovery of the new features of C#8. News are many, and there is much to learn, not least because they are already working on version 9\u2026<\/p>\n\n\n\n
            See you at the next article!<\/p>\n\n\n\n\n","protected":false},"excerpt":{"rendered":"
            Let\u2019s finish the analysis of new features in C# 8<\/p>\n","protected":false},"author":196716244,"featured_media":27386,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"off","_et_pb_old_content":"","_et_gb_content_width":"","_coblocks_attr":"","_coblocks_dimensions":"","_coblocks_responsive_height":"","_coblocks_accordion_ie_support":"","inline_featured_image":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_wpcom_ai_launchpad_first_post":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"{title}\n\n{excerpt}\n\n{url}","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"_wpas_customize_per_network":false,"jetpack_post_was_ever_published":false},"categories":[688637524],"tags":[688637384],"class_list":["post-28816","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-en","tag-c-en"],"yoast_head":"\nNew features of C# 8: part two - Blexin<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"New features of C# 8: part two - Blexin\" \/>\n<meta property=\"og:description\" content=\"Let\u2019s finish the analysis of new features in C# 8\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/\" \/>\n<meta property=\"og:site_name\" content=\"Blexin\" \/>\n<meta property=\"article:published_time\" content=\"2020-02-19T22:45:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-05-20T16:40:37+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/i2.wp.com\/blexin.com\/wp-content\/uploads\/2020\/12\/image00-7.png?fit=1024%2C608&ssl=1\" \/>\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\n\t<meta property=\"og:image:height\" content=\"608\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Francesco Vastarella\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Francesco Vastarella\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/blexin.com\\\/en\\\/blog-en\\\/new-features-of-c-8-part-two\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/en\\\/blog-en\\\/new-features-of-c-8-part-two\\\/\"},\"author\":{\"name\":\"Francesco Vastarella\",\"@id\":\"https:\\\/\\\/blexin.com\\\/en\\\/#\\\/schema\\\/person\\\/388dae0ca9df603c88b5e41e29cf2d4d\"},\"headline\":\"New features of C# 8: part two\",\"datePublished\":\"2020-02-19T22:45:00+00:00\",\"dateModified\":\"2021-05-20T16:40:37+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/en\\\/blog-en\\\/new-features-of-c-8-part-two\\\/\"},\"wordCount\":1427,\"image\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/en\\\/blog-en\\\/new-features-of-c-8-part-two\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/i0.wp.com\\\/blexin.com\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/image00-7.png?fit=1024%2C608&ssl=1\",\"keywords\":[\"C#\"],\"articleSection\":[\"Blog\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/blexin.com\\\/en\\\/blog-en\\\/new-features-of-c-8-part-two\\\/\",\"url\":\"https:\\\/\\\/blexin.com\\\/en\\\/blog-en\\\/new-features-of-c-8-part-two\\\/\",\"name\":\"New features of C# 8: part two - Blexin\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/en\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/en\\\/blog-en\\\/new-features-of-c-8-part-two\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/en\\\/blog-en\\\/new-features-of-c-8-part-two\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/i0.wp.com\\\/blexin.com\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/image00-7.png?fit=1024%2C608&ssl=1\",\"datePublished\":\"2020-02-19T22:45:00+00:00\",\"dateModified\":\"2021-05-20T16:40:37+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/en\\\/#\\\/schema\\\/person\\\/388dae0ca9df603c88b5e41e29cf2d4d\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/blexin.com\\\/en\\\/blog-en\\\/new-features-of-c-8-part-two\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/blexin.com\\\/en\\\/blog-en\\\/new-features-of-c-8-part-two\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blexin.com\\\/en\\\/blog-en\\\/new-features-of-c-8-part-two\\\/#primaryimage\",\"url\":\"https:\\\/\\\/i0.wp.com\\\/blexin.com\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/image00-7.png?fit=1024%2C608&ssl=1\",\"contentUrl\":\"https:\\\/\\\/i0.wp.com\\\/blexin.com\\\/wp-content\\\/uploads\\\/2020\\\/12\\\/image00-7.png?fit=1024%2C608&ssl=1\",\"width\":1024,\"height\":608},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/blexin.com\\\/en\\\/blog-en\\\/new-features-of-c-8-part-two\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/blexin.com\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"New features of C# 8: part two\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/blexin.com\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/blexin.com\\\/en\\\/\",\"name\":\"Blexin\",\"description\":\"Con noi \u00e8 semplice\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/blexin.com\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/blexin.com\\\/en\\\/#\\\/schema\\\/person\\\/388dae0ca9df603c88b5e41e29cf2d4d\",\"name\":\"Francesco Vastarella\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/3b8deedae8f35372d5fba49f918006fb0a58a2943aff6ae52d3ff188e0c441bb?s=96&d=identicon&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/3b8deedae8f35372d5fba49f918006fb0a58a2943aff6ae52d3ff188e0c441bb?s=96&d=identicon&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/3b8deedae8f35372d5fba49f918006fb0a58a2943aff6ae52d3ff188e0c441bb?s=96&d=identicon&r=g\",\"caption\":\"Francesco Vastarella\"},\"url\":\"https:\\\/\\\/blexin.com\\\/en\\\/author\\\/francesco-vastarellablexin-com\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"New features of C# 8: part two - Blexin","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/","og_locale":"en_US","og_type":"article","og_title":"New features of C# 8: part two - Blexin","og_description":"Let\u2019s finish the analysis of new features in C# 8","og_url":"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/","og_site_name":"Blexin","article_published_time":"2020-02-19T22:45:00+00:00","article_modified_time":"2021-05-20T16:40:37+00:00","og_image":[{"width":1024,"height":608,"url":"https:\/\/i2.wp.com\/blexin.com\/wp-content\/uploads\/2020\/12\/image00-7.png?fit=1024%2C608&ssl=1","type":"image\/png"}],"author":"Francesco Vastarella","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Francesco Vastarella","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/#article","isPartOf":{"@id":"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/"},"author":{"name":"Francesco Vastarella","@id":"https:\/\/blexin.com\/en\/#\/schema\/person\/388dae0ca9df603c88b5e41e29cf2d4d"},"headline":"New features of C# 8: part two","datePublished":"2020-02-19T22:45:00+00:00","dateModified":"2021-05-20T16:40:37+00:00","mainEntityOfPage":{"@id":"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/"},"wordCount":1427,"image":{"@id":"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/blexin.com\/wp-content\/uploads\/2020\/12\/image00-7.png?fit=1024%2C608&ssl=1","keywords":["C#"],"articleSection":["Blog"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/","url":"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/","name":"New features of C# 8: part two - Blexin","isPartOf":{"@id":"https:\/\/blexin.com\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/#primaryimage"},"image":{"@id":"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/#primaryimage"},"thumbnailUrl":"https:\/\/i0.wp.com\/blexin.com\/wp-content\/uploads\/2020\/12\/image00-7.png?fit=1024%2C608&ssl=1","datePublished":"2020-02-19T22:45:00+00:00","dateModified":"2021-05-20T16:40:37+00:00","author":{"@id":"https:\/\/blexin.com\/en\/#\/schema\/person\/388dae0ca9df603c88b5e41e29cf2d4d"},"breadcrumb":{"@id":"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/#primaryimage","url":"https:\/\/i0.wp.com\/blexin.com\/wp-content\/uploads\/2020\/12\/image00-7.png?fit=1024%2C608&ssl=1","contentUrl":"https:\/\/i0.wp.com\/blexin.com\/wp-content\/uploads\/2020\/12\/image00-7.png?fit=1024%2C608&ssl=1","width":1024,"height":608},{"@type":"BreadcrumbList","@id":"https:\/\/blexin.com\/en\/blog-en\/new-features-of-c-8-part-two\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blexin.com\/en\/"},{"@type":"ListItem","position":2,"name":"New features of C# 8: part two"}]},{"@type":"WebSite","@id":"https:\/\/blexin.com\/en\/#website","url":"https:\/\/blexin.com\/en\/","name":"Blexin","description":"Con noi \u00e8 semplice","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blexin.com\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/blexin.com\/en\/#\/schema\/person\/388dae0ca9df603c88b5e41e29cf2d4d","name":"Francesco Vastarella","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/3b8deedae8f35372d5fba49f918006fb0a58a2943aff6ae52d3ff188e0c441bb?s=96&d=identicon&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/3b8deedae8f35372d5fba49f918006fb0a58a2943aff6ae52d3ff188e0c441bb?s=96&d=identicon&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/3b8deedae8f35372d5fba49f918006fb0a58a2943aff6ae52d3ff188e0c441bb?s=96&d=identicon&r=g","caption":"Francesco Vastarella"},"url":"https:\/\/blexin.com\/en\/author\/francesco-vastarellablexin-com\/"}]}},"jetpack_publicize_connections":[],"jetpack_shortlink":"https:\/\/wp.me\/pcyUBx-7uM","jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/i0.wp.com\/blexin.com\/wp-content\/uploads\/2020\/12\/image00-7.png?fit=1024%2C608&ssl=1","_links":{"self":[{"href":"https:\/\/blexin.com\/en\/wp-json\/wp\/v2\/posts\/28816","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blexin.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blexin.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blexin.com\/en\/wp-json\/wp\/v2\/users\/196716244"}],"replies":[{"embeddable":true,"href":"https:\/\/blexin.com\/en\/wp-json\/wp\/v2\/comments?post=28816"}],"version-history":[{"count":2,"href":"https:\/\/blexin.com\/en\/wp-json\/wp\/v2\/posts\/28816\/revisions"}],"predecessor-version":[{"id":31166,"href":"https:\/\/blexin.com\/en\/wp-json\/wp\/v2\/posts\/28816\/revisions\/31166"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blexin.com\/en\/wp-json\/wp\/v2\/media\/27386"}],"wp:attachment":[{"href":"https:\/\/blexin.com\/en\/wp-json\/wp\/v2\/media?parent=28816"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blexin.com\/en\/wp-json\/wp\/v2\/categories?post=28816"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blexin.com\/en\/wp-json\/wp\/v2\/tags?post=28816"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}