Hacker News Reader

Comment by sedatk | Hacker News Reader

`let` is just a .Select(), isn't it?

A `Select` to a tuple or anonymous class which you have to carry around all the way.

If you look at how a LINQ query gets translated to a method chain (e.g. via SharpLab or let Rider/ReSharper rewrite them) you'll notice that multiple `from`s or `let`s can become quite ugly.

To add on to what you wrote, it amazes me the number of developers that don't understand you can use .Select() to construct named object instances. I'm probably using bad terminology, but something like:

    .Select(x => new Employee { Name = x.Name, DepartmentName = x.Department.Name }).ToList();

How do these developers use .Select() then?

Into anonymous types mostly, where you can't pass the type to another method. Example:

    .Select(x => new { Name = x.Name, DepartmentName = x.Department.Name }).ToList();

Same code as I wrote, except capture in an anonymous type. The documentation practically encourages this.

Oh that's convenient, that's for sure.

Reply on news.ycombinator.com