Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 12
    It might have something to do with allocating an array, which can be a performance drag. Since .NET Core is more performance oriented, I would think that that's the reason. Commented Dec 17, 2019 at 13:24
  • 7
    Not only array allocation but also boxing of every value type. Horribly inefficient. Commented Sep 23, 2021 at 7:52
  • It neither does boxing nor array allocation Commented Jul 5, 2022 at 6:47
  • @Vlad Why not? Surely it has to do with performance considerations.. Commented Aug 28, 2022 at 6:12
  • 7
    @Vlad I think the concerns about boxing and array allocation were made about a constructor accepting a params object[] values which absence I mentioned in my answer, not the calls to HashCode.Add. Commented Aug 28, 2022 at 13:15