Gary Burd

Here's one possible workflow for users: 1. User adds the plugin binary to $PATH. The `go get` command is one way to do this. 2. User adds line to init.vim...

@vito-c I added a comment to gist showing how to fix the plugin and #29 for this specific documentation issue.

Strip the PR back to the features listed in the title and golang.org/x/net/context > context go1.7 conversion. Because my time is limited, I don't want to review or even discuss...

Thank you for reporting. Pooled connections should detect the use of the CLIENT REPLY OFF command and execute the CLIENT REPLY ON command in Close().

No, this should not be closed. The issue is not fixed.

I left comments in #448. The PR is not ready for merge: - To avoid breaking changes, the API must have the correct design from the get go. Specially, there...

> Any plans to bump the version to even 1.18? The package should work with the [supported versions of Go](https://github.com/golang/go/wiki/Go-Release-Cycle#release-maintenance). You can bump the go.mod file up to 1.16.

Help wanted: Describe the subset of the package API that will work in the browser and describe how that API will be implemented in the browser.

Please generate the profiles with the latest version of the package. The recent change to pool flate readers and writes should help.

@FZambia Thank you for posting the profile information. Counters should be added [here](https://github.com/gorilla/websocket/blob/17634340a83afe0cab595e40fbc63f6ffa1d8915/compression.go#L17) and [here](https://github.com/gorilla/websocket/blob/17634340a83afe0cab595e40fbc63f6ffa1d8915/compression.go#L40) to determine how effective the pool is. Perhaps there's a code path where the flate...