Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

23
  • \$\begingroup\$ Is it "local date at 00:00:00" + n seconds or "local date at local time" + n seconds? \$\endgroup\$ Commented Feb 15, 2021 at 13:46
  • \$\begingroup\$ In my case, putting new Date() gives the date at my local time, but that might not be true in other languages. It depends on the language \$\endgroup\$ Commented Feb 15, 2021 at 13:47
  • 1
    \$\begingroup\$ Was the negative-number requirement to avoid solutions like sleep $n;date being a valid bash answer? I notice there's no performance requirement :P \$\endgroup\$ Commented Feb 16, 2021 at 2:14
  • 1
    \$\begingroup\$ It's generally accepted that CodeGolf answers that provably work for large test cases are fine, even if nobody has time to wait for them to finish, so for example O(e^n) or n! time and/or space complexity is fine for a problem that would normally take much shorter, like log(n) time. But when the "run-time" couldn't be sped up with a faster computer, so it can never produce an answer before the specified time, yeah that's stretching it in my opinion, too. And a different sort of reason for being slow than the usual excuse. \$\endgroup\$ Commented Feb 16, 2021 at 8:25
  • 1
    \$\begingroup\$ @LuisMendo Edited the question albeit a bit late \$\endgroup\$ Commented Feb 17, 2021 at 15:33