Project Springfield: A Cloud Service Built in F#
blogs.msdn.microsoft.com
blogs.msdn.microsoft.com
I wouldn't hold my breath for anything approaching parity.
C# "Pattern Matching" is little more than destructuring or switch on steroids.
However, much like how the compiler assists you when writing subclasseses so that you've implemented all the required methods, real Pattern Matching (F#) gives you the same guarantees from the compiler that you've handled all the possible cases appropriately. This makes real F# pattern matching much more useful than "switch with destructuring" and helps you grow your programs in a safe way. The C# way has all the same problems as the switch statement which gives no feedback about what cases you've handled.
It approaches from the other side - I don't care what the language lets me do, but what it doesn't. I think it's quite controversial and the examples are a bit contrived, but I found it really interesting.
I don't mean to knock Elixir/Phoenix though. They are very cool and intersting. Erlang/beam is.. interesting. But F#'s tooling is just fantastic.