C# 9 top-level programs and target-typed expressions

Post by nycdotnet » Tue, Mar 30, 2021, 9:48 PM UTC

belinder wrote: post #2

Unfortunately the new tricks can't be used when the codebase is still stuck on .net framework :(

Post by nycdotnet » Tue, Mar 30, 2021, 9:51 PM UTC

keithnz wrote: post #10

whoisthemachine wrote: post #9

To me, the benefit of "Target-typed new expressions" is more with bringing consistency to class-scope member declarations and method-scope member declarations, so these two can look the same, and a programmer only has to read one way of declaring new members in C#: public class MyClass { private readonly MyDependency _myDependency = new(); public void MyMethodThatDoesWork() { MyVariable variable = new(); } } As oppos…

I can't see var going anywhere, many times you aren't directly creating a new object, but getting a generated object from something ( like linq) which tends to have more complicated type signatures.

  // old:
  var x = new List>
  {
    new KeyValuePair("a", 1),
    new KeyValuePair("b", 2)
  };

  // new
  var x = new List>
  {
    new("a", 1),
    new("b", 2)
  };

Post by UweSchmidt » Tue, Mar 30, 2021, 10:00 PM UTC

WorldMaker wrote: post #21

belinder wrote: post #16

Earlier quoted context omitted.

In our case not web forms but WCF

You may want to keep an eye on CoreWCF: https://github.com/CoreWCF/CoreWCF Though as a heavy WCF user in the past, I'd suggest your best bet is simply to throw out all your binding configs, and build your own REST API or similar backend (gRPC support in .NET 5+ is something often also recommended if you want something more RPC-like and need/want a more binary-serializer like approach, though in 2021 I'd just use JSON…

Post by emodendroket » Tue, Mar 30, 2021, 10:03 PM UTC

danielovichdk wrote: post #19

I have been programming with c# since 2000 i think. But I do not like where the languages is going. It is becoming way to loose in a sense and it seems that it wants more than it should. If you want to do functional programming, pick a fp language. If you want to do dynamic typed programming pick a dp language. Sure you can mix some things in, but c# is becoming way to scattered imo. And it's not pretty i think.

Post by emodendroket » Tue, Mar 30, 2021, 10:05 PM UTC

thrower123 wrote: post #23

danielovichdk wrote: post #19

I have been programming with c# since 2000 i think. But I do not like where the languages is going. It is becoming way to loose in a sense and it seems that it wants more than it should. If you want to do functional programming, pick a fp language. If you want to do dynamic typed programming pick a dp language. Sure you can mix some things in, but c# is becoming way to scattered imo. And it's not pretty i think.

I think I'm going to get diabetes from all the syntax sugar... On the more substantive changes, it feels a little like the language designers have been looting F#. Combined with how fast Dotnet Core is moving and how many breaking changes there are there, it does feel like things are getting very fragmented. Stasis isn't good either; just witness the decade or so of stagnation after Java 1.6 as the Sun -> Oracle tran…