Yuta Hinokuma

@relrelb I fixed conflict. >> Welome! I think instant::Instant can be used in place of the proposed RuffleDuration. instant is already a dependency of ruffle-core, and currently being used in...

@Herschel Thanks for the review. I fixed the your review points.

@Herschel This, issue has been without activity for a long time, can I try to work on it?

@n0samu @Herschel I tried use `std::time::Duration` However, as noted in this PR, the `cargo:test://regression_tests::as3_sound_embeddedprops` test case fails. https://github.com/higumachan/ruffle/pull/1 One possible reason for this is that the original floating-point data was...

@Herschel Thank you for response! OK, I would like to implement the policy of adding `Duration(f64)` in `ruffle_core`.

@vadixidav I'd like to implement this one, how about you?

this is my wasmtime version `wasmtime 0.30.0`.

I think this problem core is that codes. https://github.com/chronotope/chrono/blob/v0.4.19/src/sys/unix.rs#L80-L104 https://github.com/chronotope/chrono/blob/main/src/offset/local.rs#L27-L31 `libc::localtime_r(&sec, &mut out)` seems to return `tm_yday` for 1970 or earlier in the WASM environment, and `-365` for January 1....

@mosuka Sorry for the confusion, we have not yet resolved this issue. That is why we are making it a Draft. At this time, this PR only highlights test cases...

@mosuka I added this problem small case test. https://github.com/lindera-morphology/lindera/pull/348/files#diff-1c519c1711701bfeb51dfbe2bfe7d812bc58bae9c89375869d31560a5b05431aR814-R833 But I do not know what to do when such a text "億兆" comes. In my idea - "1_0000_0000_0000_0000_0000" (1_0000_0000_0000 *...