vimpunk

Just ran into this. I'd like to see that autogroup removed too, there is no reason for it to exist.

Hey, thanks for your response! I completely neglected to mention my platform, which is Linux, so not using homebrew, and python came preinstalled on my system, as did vim, I...

@jparr721 Thanks for linking in that issue, I must have missed it when checking for similar ones. Indeed, greenlet seems to be the culprit for me as well.

@Shougo importing neovim in a python3 interpreter does work, hence my confusion as to why it doesn't work from within vim.

@carllerche Those are fair points. Maybe this could be a separate trait implemented only by buffers that abstract over contiguous memory, such as `BytesMut` (at least as far as I...

@ice1000 Thanks for the quick reply. This is what's in the Cargo.toml of our grpc crate: ``` [dependencies] futures = "0.1.16" grpcio = "0.4.4" protobuf = "~2" [build-dependencies] protoc-grpcio =...

That could be a future optimization for sure, but I think for now something simpler is enough. Besides, that solution would not fix incompatibility with mac/darwin/bsd, so someting more generic...

The license is mentioned in the cargo manifest. Does this suffice or is it still good practice to include license files?

Just saw this: > is TorrentFile really supposed be public? I just see all its methods are pub and have detailed doc comments, but the struct itself is pub(crate) It's...

@ExceptionallyHandsome I thought it was sufficient to make a type's visibility restricted without having to alter its methods' visibility, but I wasn't sure what is actually good practice in this...