{"action":"created","issue":{"url":"https://api.github.com/repos/zshipko/rust-kv/issues/1","repository_url":"https://api.github.com/repos/zshipko/rust-kv","labels_url":"https://api.github.com/repos/zshipko/rust-kv/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/zshipko/rust-kv/issues/1/comments","events_url":"https://api.github.com/repos/zshipko/rust-kv/issues/1/events","html_url":"https://github.com/zshipko/rust-kv/issues/1","id":301488510,"number":1,"title":"Future direction?","user":{"login":"rnewman","id":91722,"avatar_url":"https://avatars2.githubusercontent.com/u/91722?v=4","gravatar_id":"","url":"https://api.github.com/users/rnewman","html_url":"https://github.com/rnewman","followers_url":"https://api.github.com/users/rnewman/followers","following_url":"https://api.github.com/users/rnewman/following{/other_user}","gists_url":"https://api.github.com/users/rnewman/gists{/gist_id}","starred_url":"https://api.github.com/users/rnewman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rnewman/subscriptions","organizations_url":"https://api.github.com/users/rnewman/orgs","repos_url":"https://api.github.com/users/rnewman/repos","events_url":"https://api.github.com/users/rnewman/events{/privacy}","received_events_url":"https://api.github.com/users/rnewman/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2018-03-01T17:18:15Z","updated_at":"2018-03-05T16:32:31Z","closed_at":null,"author_association":"NONE","body":"Hello!\r\n\r\nCoincidentally, I have also been working on a wrapper around LMDB.\r\n\r\nI've spent some time working on things that I don't yet see represented here:\r\n\r\n- Correctly restrict to one handle per process via a 'manager'.\r\n- Integer-keyed LMDB stores.\r\n- Key-typed generic stores, so if you want a store keyed off URIs or integers only, Rust will enforce your constraint.\r\n- More detailed error wrapping via `failure`.\r\n- Encoding and decoding of values via `bincode`/`serde`, so it can handle storage of almost any serializable object.\r\n- Tagging of types so we know which deserialization to apply.\r\n\r\nNaturally I'd like to avoid wasted effort in any direction, and either merge some features, use existing libraries as layers, or clarify design decisions.\r\n\r\nWhat's your plan for the future of your library? Do you see it as relatively stable as is (that is, you're already meeting your own needs), or are you hoping to grow it into something more substantial?"},"comment":{"url":"https://api.github.com/repos/zshipko/rust-kv/issues/comments/370478388","html_url":"https://github.com/zshipko/rust-kv/issues/1#issuecomment-370478388","issue_url":"https://api.github.com/repos/zshipko/rust-kv/issues/1","id":370478388,"user":{"login":"zshipko","id":332534,"avatar_url":"https://avatars1.githubusercontent.com/u/332534?v=4","gravatar_id":"","url":"https://api.github.com/users/zshipko","html_url":"https://github.com/zshipko","followers_url":"https://api.github.com/users/zshipko/followers","following_url":"https://api.github.com/users/zshipko/following{/other_user}","gists_url":"https://api.github.com/users/zshipko/gists{/gist_id}","starred_url":"https://api.github.com/users/zshipko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zshipko/subscriptions","organizations_url":"https://api.github.com/users/zshipko/orgs","repos_url":"https://api.github.com/users/zshipko/repos","events_url":"https://api.github.com/users/zshipko/events{/privacy}","received_events_url":"https://api.github.com/users/zshipko/received_events","type":"User","site_admin":false},"created_at":"2018-03-05T16:32:31Z","updated_at":"2018-03-05T16:32:31Z","author_association":"OWNER","body":"Ah I didn't quite realize this is a semi-official Mozilla project! I will keep up with developments on `rkv` and do my best to contribute. Feel free to let me know once `rkv` is ramping up and I am happy to get more involved if you need some additional help.\r\n\r\nIf it makes most sense to pour all efforts into `rkv` then I can get on board with that, but for now I will continue to develop `kv`.\r\n\r\nLet's definitely not close the door on combining efforts, but perhaps we should wait for both `kv` and `rkv` to be developed further, since there is no real consequence to having both at the moment (other than some slight code duplication)."}}
{"actor":{"display_login":"zshipko"}}