Jarrett Revels

`TheVeryBestOneTrueBenchmarkPackage.jl`? 😛 `Benchmarking.jl` sounds fine to me, but not sure if it's worth the churn. What's the package renaming process like? Just rename everything here and register as a new...

I'm all for this if somebody can come up with a correct implementation that doesn't end up being too magical. AFAICT the proposed implementation above is unfortunately broken, for example...

@jlperla If students are still having trouble understanding benchmark scope (which is indeed a complicated thing in Julia), perhaps the easiest way to avoid the problem is to just teach...

I guess calls e.g. https://github.com/JuliaCI/BenchmarkTools.jl/blob/00cc39e3e7043e0c9146921672f36e29e7c498e2/src/execution.jl#L347 need to be fully qualified

there are likely still issues here if people want to tackle them

That's probably a good idea. I think I'd want to alter the current approach to spit out HTML rather than markdown, leaving open the possibility for cool interactive JS stuff...

cc @ivirshup, you're probably working on other things but just in case you have ideas

@ahwillia This issue is just for generating reports from benchmark data, which is separate from `Base.Pkg` support for BenchmarkTools (though both would be nice). From [previous discussions on that front](https://github.com/JuliaLang/julia/issues/13893#issuecomment-170387156),...

> Would it make sense to try to put some kind of confidence interval on the time based on all of the samples? This is quite tricky to do correctly...

It might be the case that we can't easily "fix" this due to how things parse, so the action item here is to change the documentation to use `begin...end` instead...