Chocobo1

@xavier2k6 Feel free to chime in if you are interested in this PR.

>I wonder if it's difficult to implement client side bencode parser in JS? It is very possible that one (or more) already exists. FYI, there certainly exists bencode encoder/decoder library...

>"bencode" format is independent from BitTorrent so generic "bencode" decoder should not depend on it too. They had deficiencies in their implementations. Not fully conform with the spec.

@Piccirello Thank you!

>I decided to investigate this with callgrind, and I found that ~17% of the total CPU usage was in [parse_url_components](https://github.com/arvidn/libtorrent/blob/c31d90b59ffb3910b6d36ba7ad914e0e489d2b6c/src/parse_url.cpp#L43-L148), specifically in the calls to std::find, which, it seems aren't...

I don't have much to add and I just found this interesting post: https://gms.tf/stdfind-and-memchr-optimizations.html#is-stdfind-faster-as-memchr @bolshoytoster Could you share your compiler version? >I'd like to know if this would be welcome...

>@Chocobo1 Do you know why the Windows build in this repo (in-general) always show a green tick overall even when there's been a failure of say even 1 test? Not...

>It look like your fix broke the Windows CI run. Perhaps more fixes are needed? How do I fix it?

Please add description of "why" is it done.

@stalkerok Thank you!