Danyel

There is already a crate, but it only exposes the `imdl::run` function that takes no arguments. I'd already be more than happy if there were just a second function à...

This library uses the underlying C++ library provided by rarlabs. Unfortunately it does not have any native parsing of archive contents, and I don't even know how an archive is...

My worry is: - I'm not sure how much overhead the `map_span` method has to convert spans for e.g. string inputs. So I'm not sure if an extension crate would...

I've tried with the [linux](https://github.com/torvalds/linux) codebase, it's ~2 GiB (528MiB packed) with ~100k files. Extracting that rar file with the library takes over a minute for me. Extracting with `rar...

I found out why `unrar x` is so fast: it uses multithreading (11 threads). Unfortunately the library does not provide any parameters for multithreaded extraction, so one must open multiple...

> Nice! > > I'm confused with the fact that the library doesn't allow for multithreading though, doesn't the `unrar` binary use that library? How does that do multithreading? The...

@AntoniosBarotsis is there anything you feel has to be done on the library side? Otherwise we can close this, right?

@ttys3 thanks for investigating. Either way, unrar uses multiple threads even if it not advertised. To verify this, I had manually compiled unrar with print statements, and for example here,...

`.define("RAR_SMP", None)` enables `RAR_SMP` flag (it is similar to passing `-DRAR_SMP` in `c++/gcc`, just without a value, that's why the `None`), although I don't remember what specifically the `RAR_SMP` does...

I had an untitled buffer in Zed where I kept some very important notes, it grew rather large and I just fell victim to this bug. The entire buffer with...