Просто лучший!

Understand the wrong question and make the initial scheme complicated. Returns a string showing the power of the power and the entire equation process.

This shouldn't be best practices, condensed code (1 line), many conversions

I think you misunderstand the problem. The problem is that there is no a guaranteed order of execution of all of the times that the lambda expression is executed.

Not an issue - int is a value type, meaning p is passed by value and not by reference. So you can mutate it all you like inside the method and it will not affect the original parameter from the caller's perspective.

Not an issue - int is a value type, meaning p is passed by value and not by reference. So you can mutate it all you like inside the method and it will not affect the original parameter from the caller's perspective.

that is kind of "worst practices"

Since query methods are lazy, mutation inside a lambda passed to a query is a very bad idea.

This is definitely not a best practice...

It looks handy and short but that's it.

Too many conversions, too many things in the very same line, I wouldn't write production code like that...