6 ms·
I attempted to implement the Temporal spec myself and it really isn't fun. After the tc39 meeting in May, I also switched to `temporal_rs` for `yavashark`. My o
by sharktheone 1y ago
I attempted to implement the Temporal spec myself and it really isn't fun. After the tc39 meeting in May, I also switched to `temporal_rs` for `yavashark`. My own implementation ways everything else than optimal, I didn't support the RFC9557 timeformat.
In theory you could even use temporal_rs to provide an perfect polyfil with wasm.
- nekevss 1y agoWe could do a WASM FFI target. I have thought about it lol My only concern is that temporal_rs packages it's own time zone data, which may make the WASM package a little heavy, so I've been inclined to leave the polyfill up to fullcalendar's implementation.
- Manishearth 1y agoDiplomat has a wasm backend so it would even be really easy to produce a WASM ffi target with idiomatic JS and TS bindings. Also, Diplomat supports traits and callbacks so you could actually make the timezone impl pluggable. Though we don't currently have JS support for that. But also tz info isn't that big I think...