Simonas Kazlauskas

> Otherwise though I'd think we'd rather not be in the business of naming wasm snapshots. Sorry if I made the impression that it'd be a prerogative of anybody else...

A relevant discussion is https://github.com/WebAssembly/spec/issues/870. It occurred a long while ago, so I don't know if the perception of the topic has changed since, but it largely reaffirms my impression...

Just a wild shot, couldn’t the skipping be implemented in the `drop` implementation of the value returned by the iterator? While it wouldn’t resolve the problem in general, it could...

I’m trying to understand the issue here, and I think the only truly problematic part here is the fact that the name of the custom section is validated for UTF-8...

Ohhh, I see, yeah. --- I gave this buffering issue a think while taking a walk and realized this is _also_ an issue with all the other kinds of sections...

[wa2c/cifs-documents-provider](https://github.com/wa2c/cifs-documents-provider) seems to be a working drop-in replacement.

@cjgillot you want to keep reviewing this to the end or should I take a look at this still?

Wouldn't implementing lock algorithms on top of futex et al. effectively mean that both the `parking_lot` based implementations and these other algorithms receive less test/use coverage overall? Or is there...

Verified reproducible with 2.1.2 as well. ``` 2022/10/01 19:35:37 [main:3] Liquidsoap 2.1.2 2022/10/01 19:35:37 [main:3] Using: graphics=5.1.2 bytes=[distributed with OCaml 4.02 or above] posix-time2=2.0.0 pcre=7.5.0 sedlex=2.5 menhirLib=20220210 curl=0.9.2 uri=4.2.0 dtools=0.4.4...

I’ve done some additional investigation using gstreamer as a client/server and looking at wireshark. First, with `liquidsoap` as both a server & client, wireshark displays a bunch of UDT handshake...