Folkert de Vries

Based on the spec, I don't think there is any guarantee that there is a consistent value that separates out-of-bounds access RangeErrors from other RangeErrors. All getters are based on...

that does not add up. That confirmed bad commit only changes stuff for wasm. Or is there a gap (i.e. other commits) between the good and bad commits?

as a datapoint, this is what we do in `ntpd-rs`: We have an existing udp socket. Based on that socket we create an additional "exceptional condition" socket that becomes readable...

This is the profiling result of elm-format on elm-spa-example: ``` elm-format +RTS -p -RTS src/ src/Api/Endpoint.elm src/Article/Body.elm src/Article/Comment.elm src/Article/Feed.elm src/Article/Slug.elm src/Article/Tag.elm src/Page/Article.elm src/Page/Article/Editor.elm src/Page/Blank.elm src/Page/Home.elm src/Page/Login.elm src/Page/NotFound.elm src/Page/Profile.elm src/Page/Register.elm src/Page/Settings.elm...

this was implemented as https://github.com/roc-lang/roc/pull/4526

doing some cross-linking here. In https://github.com/tokio-rs/tokio/pull/5566, `Interest::PRIORITY` and `AsyncFd::ready` have been added. On linux (and android, I guess) that makes it possible to wait for `EPOLLPRI` (cc @Blub) I've now...

It looks like `mio` recently added the `PRIORITY` interest https://docs.rs/mio/0.8.6/src/mio/interest.rs.html#49. When tokio updates its version of `mio`, tokio could expose this interest (for linux and android, anyway). To me, that...

does this stil reproduce? @lukewilliamboswell maybe you can check this on aarch64? on x86_64 this seems to work fine ``` » Dict.fromList [("foo", 123i64)] @Dict { buckets: [{ dataIndex: 0,...

for context, what sort of program hits this `todo!()`?

do you think you can make a failing test case? I'm not sure how we don't hit this in the test suite. We do run that with `llvm-wasm` so it...