---
title: "Comment by Francesco Formenti on \"LINQ gems: Troubles with Out Parameters\" | Hashnode"
description: "Hi Jan, I really appreciate your linq gems! This one pointed me to another solution that, I hope, you and your blog readers could like. It is similar to the val"
url: "https://hashnode.com/posts/linq-gems-out-parameters/605c235747b0d2243d4ad4b4/comment/63230f438350c8888bf30d82"
---

[Discussion](https://hashnode.com/posts/linq-gems-out-parameters/605c235747b0d2243d4ad4b4)

Comment [LINQ gems: Troubles with Out Parameters](https://hashnode.com/posts/linq-gems-out-parameters/605c235747b0d2243d4ad4b4)

[Francesco Formenti](https://hashnode.com/@formentz)

[Sep 15, 2022](https://hashnode.com/posts/linq-gems-out-parameters/605c235747b0d2243d4ad4b4/comment/63230f438350c8888bf30d82)

Hi Jan, I really appreciate your linq gems! This one pointed me to another solution that, I hope, you and your blog readers could like. It is similar to the value tuple you mentioned:

Using the `new` keyword to create an anonymous type in a `let` clause:

```
var query =
      from word in testWords
      let entry = new
      {
          word,
          usage = wordUsage.TryGetValue(word, out var u) ? u : 0,
      }
      orderby entry.usage
      select (entry.word, entry.usage);
```

Or maybe you can directly do:

```
//[...]
select entry;
```

to use the whole anonymous object as a result.
