Time forward testing about proposal-temporal HOT 4 CLOSED

Do people usually do that testing from Node or in the browser? It seems like something that needs to be provided by the engine host environment rather than from within the script itself so that it would also affect Date (and anything else, like native modules) and not just the new API.

from proposal-temporal.

I make heavy use of NodaTime's IClock interface in my .NET code. It isn't exactly proper 'time forward' testing where the entire environment is rolled forward, but it can still be used to test paths around leap year and DST transitions - which I find quite useful.

from proposal-temporal.

It seems problematic to introduce such a feature without heavy host integration. E.g. what is its impact on setTimeout, event.timeStamp, etc. I'd suggest leaving it out of this proposal; it has enough weight to be a large proposal in its own, and if done properly will require stakeholders outside TC39.

from proposal-temporal.

Can we close this as unwanted? Especially in light of the debate in #73 ?

from proposal-temporal.