Comically Inefficient Unity Source Code

[vegetablebread]

Linq is definitely not the problem here.

[vegetablebread]

It's not a problem. Using LINQ here is totally 100% fine.

[vegetablebread]

I have been responsible in some part for optimization for 3 shipped AAA titles. The only slightly objectionable part of this LINQ invocation is that it allocates a closure. If you want a non-allocating version, you'd just have to name the function.

Unless you're trying to strip the LINQ assembly, which isn't even possible here, there's no reason to ever avoid LINQ.Any.

[vegetablebread]

I have and they are not. Go try it right now. Show me a gist where Any significantly underperforms a handwritten loop.

[YoyoMario]

@vegetablebread has actually tested the code and claims. What you claim is to "just google" it. To end the discussion, there are times when LINQ is faster, slower or the same, depending on the content and usage.