-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide longer names #122
Comments
I vote C. because it seems the clearest and not-too-verbose alternative and I like the pun ;-) |
what about also (manipulated suggestion from the other options in #100) D. |
I like |
why not |
As Charimarks.jl has gained popularity and started to get used outside of the REPL, it makes sense to move to longer names for
@b
and@be
.What sort of longer names do folks want?
A.
@btime/@benchmark
does not make sense because@b
, unlikeBencharmkTools.@btime
, neither prints runtime data nor returns the evaluation resultB.
@benchmark_summary
/@benchmark_full
works, though very verbose, and precludes adding an even more informative version that saves more dataC.
@bench
/@benchmark
is fun and silly and concise while still being clear that we're benchmarking. It still relies on the pun: shorter name = shorter results.I would implement this by adding long names as an option and then maybe deprecating the use of short names in packages and scripts. I do not currently plan to deprecate the use of short names at the REPL.
Alternatively, I could export the long names and publicize the short alternatives, like Unitful.
Originally posted by @LilithHafner in #100 (comment)
The text was updated successfully, but these errors were encountered: