07:53
<BrownJenkin>
is it worth suggesting Math.TAU? i have to Math.TAU = 2 * Math.PI at the top every time.
08:18
<Domenic>
https://esdiscuss.org/topic/math-tau
08:20
<Domenic>
https://github.com/rwaldron/tc39-notes/blob/master/meetings/2014-07/jul-31.md#51-mathtau
09:44
<BrownJenkin>
lame.
09:45
<BrownJenkin>
even python got a math.tau
10:39
<rkirsling>
wow, the relevant Python issue number for that was apparently 12345: https://bugs.python.org/issue12345
10:41
<rkirsling>
lol, Guido on 2016-08-10: "I'm just going to do this." benevolent dictator indeed
10:42
<rkirsling>
to be fair, that was a full two years after the above TC39 discussion (which itself was before the current TC39 Process began)
10:44
<rkirsling>
prior art is important, so I think it'd be valid to reraise; the presentation would just require usage data
10:46
<rkirsling>
('cause one figures it would basically either get blocked at Stage 0 or go straight to Stage 3)
10:54
<rkirsling>
as usual, it sucks that github search is so useless
11:34
<annevk>
The rationale there is pretty weak too "might make Python popular"
12:11
<bakkot>
github search is pretty decent these days I think - https://github.com/search?q=language%3Apython+math.tau&type=code
12:40
<annevk>
bakkot: if you compare that to results for math.pi it really doesn't seem worth the time
12:55
<BrownJenkin>
it's a line of code
12:56
<BrownJenkin>
how much time is that?
13:01
<Andreu Botella>
it might be a line of code for you to polyfill, but to add it to the language takes consensus and definitely more than one line in the spec and in browsers' code
13:34
<rkirsling>
the time in question here is primarily referring to the fact that the committee has finite time to consider proposals in general
13:36
<rkirsling>
if we spent an hour battling over whether this is worth it, that'd be an hour we didn't spend talking about another proposal, which could potentially mean that some other proposal comes to fruition months later than it otherwise would have
13:36
<annevk>
it's also the time for people writing educational material, tests, implementations, web developers trying to understand code, etc.
13:37
<rkirsling>
you're not wrong but I feel like it's not hard to find people passionate enough about tau to do that willingly :p
14:01
<BrownJenkin>
it might be a line of code for you to polyfill, but to add it to the language takes consensus and definitely more than one line in the spec and in browsers' code
sorry. you are right. this is a very important piece of software and change needs to have a very good reason.
17:33
<ljharb>
i would LOVE to add Math.TAU but yeah it'll be a tough sell for some, even tho it's literally just a property and a number
23:36
<jasew>
https://github.com/rust-lang/rust/issues/66770