On Friday, 4 April 2014 at 08:16:20 UTC, Paulo Pinto wrote:
Says who? And slow to whom?

1 - Write correct code

2 - Use a profiler, if the code isn't fast enough for the use case being written for

3 - If desired use case isn't there, use the profiler information to improve the specific hotpaths in need of tuning.

I see too many people micro-optimize for nothing.

--
Paulo

While this is true in general, spotting performance overhead from using bigints everywhere in profiler can be rather tricky because it will be evenly spread across the program. Micro-optimizations are bad but this is not very practical example.

Reply via email to