Net 9.0 LINQ Performance Improvements

Re:Net 9.0 LINQ Performance Improvements by mythz on Friday October 18, 2024 @10:53AM (#41880000)

This is a custom expression language to work within the expressive limitations of the language:

    create.select(BOOK.TITLE)
      .from(BOOK)
      .where(BOOK.PUBLISHED_IN.eq(2011))
      .orderBy(BOOK.TITLE)

If Java supported LINQ you'd be able to use a more intuitive and natural Java expression syntax instead:

    create.from<Book>()
     .where(x -> x.publishedIn == 2011)
     .orderBy(x -> x.title)
     .select(x -> x.title);

[ Parent | on HN ]

Re:Net 9.0 LINQ Performance Improvements by pjmlp on Friday October 18, 2024 @10:58AM (#41880030)

Java streams are what you're looking for.

If you insist in telling LINQ === EF, well that isn't what most folks in .NET use System.Linq for.

And back to the ORM thing, jOOQ is one way, there are others, and even if it isn't 1:1 to "from x select whatever" the approach exists.

[ Parent | on HN ]

Re:Net 9.0 LINQ Performance Improvements by mythz on Friday October 18, 2024 @11:04AM (#41880082)

> If you insist in telling LINQ === EF

I don't use EF, nor have I ever mentioned it.

You're replying to a thread about what it takes to implement a LINQ provider, which was dismissed as every high level language implements it with iterables, then proceed to give non-equivalent examples.

[ Parent | on HN ]

Re:Net 9.0 LINQ Performance Improvements by recursive on Friday October 18, 2024 @12:31PM (#41880971)

IQueryable<> manipulation has other tools available to it than brute-force iteration, like streams do. Streams may be the closest thing java has, but it's still a fundamentally different thing.

[ Parent | on HN ]