[superseded] undeprecate toSeconds, toUnix is not a drop-in replacement

[timotheecour]

toUnix is not a drop-in replacement for the deprecated toSeconds; if user wants subsecond resolution with a easy to use data representation via a simple float (like in python: time.time()), toSeconds is still useful (and makes it easy to inter-operate with python timestamps for example)

[GULPF]

-1 from me. Just because something doesn't have a drop-in replacement doesn't mean that it cannot be deprecated. float does not belong in a time library in my opinion.

If we really want to bring this back we should at least name is something better. toSeconds only says what the unit of the return value is, it says nothing about what it represents. It's even more confusing now that we have times.inSeconds that does something completely different. Something like toUnixFloat would make more sense.

[narimiran]

I agree with @GULPF here, and I don't see a reason for de-deprecation. If I'm wrong and there is a good reason or if there should be a discussion about it, please open an issue in RFCs repo.