Should `now` error on wasm (not on emscripten or wasi) without wasmbind? about chrono

[pitdicker]

The clock feature is already pretty much the thing that controls if now() and Local are available.

If I remember right wasm support was quickly added to the standard library to give rust a presence in that space since the beginning. But a lot of things were just stubs that panic on use. It was the first (and maybe only?) target where the standard library lies about its capabilities.

We could remove now on wasm without the wasi target or wasmbind feature. That would indeed be a breaking change.

But if an ecosystem is build on 'pretend you support some features so you can compile, but avoid actually using xyz', it seems chrono is following the conventions for that ecosystem. What do you think?

[alexkazik]

I'm ok with how it is, I wanted to make it easier for newcomers, especially if wasmbind get's disabled by default #1164.