Refactoring by template

[dukaev]

#169

[mateusdeap]

@dukaev I don't know if you're already on this, but I believe that if you just add Ashwini's suggestions to your PR, in the issue this solves, we can merge it.

Thanks for the good work!

[mateusdeap]

If not, that's fine. Just let me know and I can take it over.

[dukaev]

@mateusdeap great. In a few days I will do this

[JuanVqz]

Thanks @dukaev, and sorry this sat for so long. You spotted this in 2019: the fast code should come first so the template is easy to read at a glance.

It has now landed on main through #242 and #243. Those go a step further: every report is named by rank (fastest/faster/fast, then slow/slower/slowest) with the winner first, and a CI linter enforces it:

fast-ruby/.github/scripts/lint-benchmarks.rb

Lines 1 to 12 in 86836b0

	# Checks that every benchmark under code/ has the same shape, so they all run,
	# print a comparison, and are measured the same way:
	#
	# - every Benchmark.ips block calls x.compare!
	# - no custom timing (Benchmark.ips(20), x.time = 20, x.warmup = 5, x.config(time: 20) in any hash syntax),
	# so every file uses the default
	# - no Benchmark.ips sits inside a method that never runs from the top of the file,
	# which would benchmark nothing at all
	# - every Benchmark.ips block states which report should win: exactly one
	# report calls `fastest` (else `faster`, else `fast`), and it comes first
	#
	# Usage: ruby .github/scripts/lint-benchmarks.rb [files...] (needs Ruby 3.3+)

All 21 files you touched now follow that order, so I'm closing this one as superseded. Thanks for pushing on it early!