Manish Goregaokar

Results 134 issues of Manish Goregaokar

Context: I maintain [`elsa`](https://docs.rs/elsa), a crate which contains append-only collections that can be appended to with only `&self` references. Recently @steffahn brought [this bug](https://github.com/Manishearth/elsa/issues/48) to my attention, where elsa's assumption...

Would be nice if the methods had docs and doctests. A lot of this can be copied from `std`

help wanted

I'd like for us to eventually have a world where rustc simply depends on compiletest-rs, and compiletest-rs lives in rust-lang Blockers: - [ ] Remove dependency on `test` crate https://github.com/Manishearth/compiletest-rs/issues/237

As I understand it we don't actually use much of the `test` crate. Given that it's also forked from rustc, perhaps we can drop that dep? Ideally we can do...

``` Traceback (most recent call last): File "report.py", line 18, in wrap.login(username,password) File "SEChatWrapper.py", line 49, in login self.br.loginChatSE() File "SEChatBrowser.py", line 67, in loginChatSE authToken = chatlogin.find('input', {"name": "authToken"})['value']...

bug

Since the SE openid is integrated, on some sites there is no confirmation message unless you enter it as a custom openid. We're doing the latter here, so we should...

We currently cache messages in `client` https://github.com/Manishearth/ChatExchange/blob/master/chatexchange/client.py#L71 However, these are not updated on edits, and it's cached indefinitely. We should have: - [ ] A way to keep these up...

Some tests are failing because pins expire. We might want to make the assertion optional ("expected failure"). I'll look into whether or not pytest supports this.

Perhaps some common room methods like `send_message` and `watch` should be reexported on `Client` with an extra room id parameter for convenience?

question