Nobuyoshi Nakada wrote: > At the developers' meeting this week, mrkn suggested `TWO_PI` instead. I don't think TWO_PI would be very useful since it misses the main point of tau, which is that tau is the correct circle constant, (and ...sbaird (Simon Baird)
This may be of interest: Guido van Rossum recently reopened the Python version of this request and is going to add tau to Python. See https://bugs.python.org/issue12345 .sbaird (Simon Baird)
Since today is 6/28, here's a pull request on trunk: * https://github.com/ruby/ruby/pull/644 See also: * http://tauday.com/state-of-the-tau Best wishes and Happy Tau Day... :)sbaird (Simon Baird)
I don't think the benchmarks are particularly relevant here. We should define Tau because it's important, not for any performance benefit.sbaird (Simon Baird)
david_macmahon (David MacMahon) wrote: > I vote -1 on this idea because the name "TAU" is used in a number of fields to represent a wide variety of things: > ... mhartl addresses this here: http://tauday.com/tau-manifesto#sec:ambiguo...sbaird (Simon Baird)
Direct link to the gist containing my patch: https://gist.github.com/1029552 Edit: mention this is a patch (pluid61's patch is better though)sbaird (Simon Baird)