--- title: From C# 1.0 to C# 15: Why Union Types Took More Than 20... description: C# 15 introduces union types after more than 20 years of language evolution. The feature lets developers explicitly declare every possible outcome of an... canonical: https://daily.dev/posts/from-c-1-0-to-c-15-why-union-types-took-more-than-20-years-to-arrive-ipitz7zry twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: From C# 1.0 to C# 15: Why Union Types Took More Than 20 Years to Arrive | daily.dev og:description: C# 15 introduces union types after more than 20 years of language evolution. The feature lets developers explicitly declare every possible outcome of an... og:url: https://daily.dev/posts/from-c-1-0-to-c-15-why-union-types-took-more-than-20-years-to-arrive-ipitz7zry og:image: https://api.daily.dev/og/posts/iPiTZ7ZrY.png og:image:alt: From C# 1.0 to C# 15: Why Union Types Took More Than 20 Years to Arrive og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # From C# 1.0 to C# 15: Why Union Types Took More Than 20 Years to Arrive **[Medium](https://daily.dev/sources/medium_js)** · 5 min read · 16 upvotes · 0 comments ## Summary C# 15 introduces union types after more than 20 years of language evolution. The feature lets developers explicitly declare every possible outcome of an operation as a distinct type, enabling the compiler to enforce exhaustive handling at compile time rather than discovering missing cases at runtime. The post traces C#'s major milestones — generics, LINQ, async/await, records — to show how each version solved a real developer pain point, and explains why union types took so long: backward compatibility requirements mean the feature touches pattern matching, type inference, tooling, serialization, and compiler analysis simultaneously. Union types are currently in preview for C# 15 / .NET 11, with GA expected November 2026. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What are union types in C# 15 and how do they work? Union types in C# 15 let a method's return type explicitly list every possible outcome, such as a login result being User, InvalidPassword, UserLocked, or UserNotFound. Using a switch expression over the union, the compiler checks that every case is handled, catching unhandled cases at compile time rather than at runtime. The feature is in preview as part of C# 15 and .NET 11, with general availability expected November 2026. _Developers modeling multi-outcome results in C# can track union types' rollout details on daily.dev before committing to the pattern._ ### Why did C# take over twenty years to add union types when languages like Rust and Swift already have them? The delay came from scope, not lack of interest. C# has always prioritized backward compatibility, and union types touch pattern matching, type inference, tooling, IntelliSense, serialization, and compiler analysis simultaneously, making it a multi-year design problem rather than a simple syntax addition, unlike languages such as F#, Rust, Swift, and Kotlin that built this in from early on. _Teams weighing language migrations over missing features like union types can compare tradeoffs on daily.dev._ ## Similar posts on daily.dev - [Explore union types in C\# 15](https://daily.dev/posts/explore-union-types-in-c-15-oygraauhf) · DevBlogs · 64 upvotes · 3 comments - [Working union types into C\#](https://daily.dev/posts/working-union-types-into-c--n1rhxnbqf) · Atomic Spin · 0 upvotes · 0 comments --- Tags: [#.net](https://daily.dev/tags/.net), [#c#](https://daily.dev/tags/c#) [View this post on daily.dev](https://daily.dev/posts/from-c-1-0-to-c-15-why-union-types-took-more-than-20-years-to-arrive-ipitz7zry) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"From C# 1.0 to C# 15: Why Union Types Took More Than 20 Years to Arrive","url":"https://daily.dev/posts/from-c-1-0-to-c-15-why-union-types-took-more-than-20-years-to-arrive-ipitz7zry","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/from-c-1-0-to-c-15-why-union-types-took-more-than-20-years-to-arrive-ipitz7zry"},"datePublished":"2026-07-22T14:06:19.772Z","dateModified":"2026-09-14T09:09:45.215Z","description":"C# 15 introduces union types after more than 20 years of language evolution. The feature lets developers explicitly declare every possible outcome of an...","image":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","thumbnailUrl":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","isAccessibleForFree":true,"articleSection":"Medium","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Medium","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/medium","url":"https://daily.dev/sources/medium_js"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/from-c-1-0-to-c-15-why-union-types-took-more-than-20-years-to-arrive-ipitz7zry","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":16},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":".net,c#","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Medium","item":"https://daily.dev/sources/medium_js"},{"@type":"ListItem","position":3,"name":"From C# 1.0 to C# 15: Why Union Types Took More Than 20 Years to Arrive"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/from-c-1-0-to-c-15-why-union-types-took-more-than-20-years-to-arrive-ipitz7zry#faq","mainEntity":[{"@type":"Question","name":"What are union types in C# 15 and how do they work?","acceptedAnswer":{"@type":"Answer","text":"Union types in C# 15 let a method's return type explicitly list every possible outcome, such as a login result being User, InvalidPassword, UserLocked, or UserNotFound. Using a switch expression over the union, the compiler checks that every case is handled, catching unhandled cases at compile time rather than at runtime. The feature is in preview as part of C# 15 and .NET 11, with general availability expected November 2026. Developers modeling multi-outcome results in C# can track union types' rollout details on daily.dev before committing to the pattern."}},{"@type":"Question","name":"Why did C# take over twenty years to add union types when languages like Rust and Swift already have them?","acceptedAnswer":{"@type":"Answer","text":"The delay came from scope, not lack of interest. C# has always prioritized backward compatibility, and union types touch pattern matching, type inference, tooling, IntelliSense, serialization, and compiler analysis simultaneously, making it a multi-year design problem rather than a simple syntax addition, unlike languages such as F#, Rust, Swift, and Kotlin that built this in from early on. Teams weighing language migrations over missing features like union types can compare tradeoffs on daily.dev."}}]} ```