New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make Neovim fully compliant with msgpack-rpc specification #1118

Closed
justinmk opened this Issue Aug 27, 2014 · 4 comments

Comments

Projects
None yet
4 participants
@justinmk
Copy link
Member

justinmk commented Aug 27, 2014

follow-up of #973 (comment)

@justinmk justinmk added this to the first release milestone Aug 27, 2014

@justinmk justinmk added the api label Aug 27, 2014

@tarruda

This comment has been minimized.

Copy link
Member

tarruda commented Aug 27, 2014

Two changes are required for us to be compliant:

@justinmk

This comment has been minimized.

Copy link
Member

justinmk commented Aug 27, 2014

A simple option would be to create an initialization function that populates a khash instance with function pointers

I'm in favor of this. If we changed to the complex approach later, it would be transparent to clients (I think?).

@aktau

This comment has been minimized.

Copy link
Member

aktau commented Aug 27, 2014

I'm in favor of this. If we changed to the complex approach later, it would be transparent to clients (I think?).

Yep, it would.

@philix

This comment has been minimized.

Copy link
Member

philix commented Aug 27, 2014

I'm in favor of this. If we changed to the complex approach later, it would be transparent to clients (I think?).

Yep, it would
👍

I didn't implement this yet because I'm short on free time. Busy with the undergraduate thesis and helping my father with his new business.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment