‹ BackHN Continuity

Thread

Performance Improvements in .NET 11

349 points · 112 comments · soheilpro

  1. dude250711 · · focus · HN ↗
    C#/.NET are very well-represented in LLM data - from enterprise back-end code to games. A language to use for sure.
    1. CharlieDigital · · focus · HN ↗
      Flip side: LLMs have to be very explicitly told to code in "modern" .NET and C# due to lack of representation in the training set.

      Case in point: extension members from C# 14 is one that LLMs commonly stumble on and requires an explicit example. It still sometimes says that this is not valid syntax.

          extension(SomeType instance)
          {
              public OtherType DoSomething() { ... }
          }
      
      Agents really struggle on this one for some reason.

      Even older releases have a few that I notice LLMs making mistakes on like use of `System.Threading.Lock` over `Object` when locking.

      1. oldmanhorton · · focus · HN ↗
        The dotnet team provides some agent plugins which solve some of these issues. I expect unions in dotnet 11 will need some skill updates too.
        1. mexicocitinluez · · focus · HN ↗
          I wonder if any of those work alongside Github Copilot (the autocomplete not actual agent).

          Because at this point I would do anything if I could get Github Copilot to understand the new language features and stop trying to constantly revert code.

          The one specific thing I'm constantly having to deny is Copilot seeing this:

              List<string> items = [];
          
          into this:

              List<string> items = new List<string>();
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.