Anthony Nowell

It seems to me that the lack of type identification on the `self` arg means you can't really get rustdoc to surface it as if it were a method on...

@krscott @softprops @deg0nz - I'm just did the same. I would happily open PRs somewhere else if there was consensus on a single repo being maintained.

I had forgotten to drop ruby 1.9.2 from the travis build. I replaced it with the latest-and-greatest 2.1.4 and now things look happy.

I believe the *right* solution is gonna be to get a library like [reqwest](https://crates.io/crates/reqwest) to target emscripten and compile down to some web API. I'd like to see it target...

Indeed. "Coming soon" hasn't been a bit misleading as I haven't done any WASM work yet. I just shook off a few massive time sinks that kept me from Quasar...

@naythanN : I'd be curious to know why you might be interested in using this crate now, since [Rust 1.58 introduced identifier capture for format strings](https://blog.rust-lang.org/2022/01/13/Rust-1.58.0.html). IMO, Rust 1.58 basically...

Correction @argoday: long ago we had discussed what you described with `error_type`, but it was never implemented (outside of common message passing). For langpacks we added the field to minimally...

> All in all, this doesn't give me enough confidence to use this lib given the ratio between noticeable imprecisions and amount of unsafe code :( Fwiw, I'm no longer...

> Documentation states that self is mutably borrowed, while it's actually immutably borrowed. I think it's the code that's incorrect, but I'm not completely sure. I don't recall my decision...

I'd actually like to use 'cp'... I think it's the same as your suggested 'sync', but semantically more like `scp`. `algo cp [-r] ... ` (bonus points for aliasing to...