@hiyosilver - did you benchmark your code? I did, and the "naive" Min/Max solution is indeed faster. C# vectorizes the search, which makes it an order of magnitude faster than a linear search with a for loop, according to my benchmark.

brother calm down lmaooo ur not releasing this

chill bro

WHAT IS THIS??

I've just wrote them an email with this idea=).

That's actually a much better idea, and should really be trivial to add.
You could even I think quite easily add statistics like speed percentile for the given language. That would make unusually slow solutions stand out and lead people to question why that might be.

That being said, I don't think this site sees a lot of development so this might be a fool's hope :P

Redundant StringBuilder floor usage.

Or as an option, developers of this web site will have add something like load tests and show avg execution time near each sulution in such test. to give developerse oppotuniti competting in whose code is the most effective. And also add the fastest code filter in here. And the same to memory usage. Also such statistic may be useful to newbe.

This is a source of the exception when a result of Pow is higher tham double.

Feels like the "Best Practices" button should be restricted or disabled entirely, since a whole bunch of people will upvote anything that's crammed into a neat one-liner as "Best Practices" even if it's horrendously inefficient.
Not that my code is exactly brilliant, but from the comments on a lot of these I get the feeling that many people are learning terrible habits.

if n is int.MaxValue than stack overflow exception.=)

if n is int.MaxValue than stack overflow exception.=)

if n is int.MaxValue than stack overflow exception.=)
Repeat 7411 times.