On Sun, Oct 15, 2017 at 8:40 PM, Nick Coghlan <ncogh...@gmail.com> wrote:
> Hopefully by the time we decide it's worth worrying about picoseconds in > "regular" code, compiler support for decimal128 will be sufficiently > ubiquitous that we'll be able to rely on that as our 3rd generation time > representation (where the first gen is seconds as a 64 bit binary float and > the second gen is nanoseconds as a 64 bit integer). > I hope we'll never see time_ns() and friends as the second generation -- it's a hack that hopefully we can retire in those glorious days of hardware decimal128 support. -- --Guido van Rossum (python.org/~guido)
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
