{"action":"created","issue":{"url":"https://api.github.com/repos/Geal/nom/issues/367","repository_url":"https://api.github.com/repos/Geal/nom","labels_url":"https://api.github.com/repos/Geal/nom/issues/367/labels{/name}","comments_url":"https://api.github.com/repos/Geal/nom/issues/367/comments","events_url":"https://api.github.com/repos/Geal/nom/issues/367/events","html_url":"https://github.com/Geal/nom/issues/367","id":189986028,"number":367,"title":"Generating binary from a struct [feature req]","user":{"login":"chifflier","id":308574,"avatar_url":"https://avatars.githubusercontent.com/u/308574?v=3","gravatar_id":"","url":"https://api.github.com/users/chifflier","html_url":"https://github.com/chifflier","followers_url":"https://api.github.com/users/chifflier/followers","following_url":"https://api.github.com/users/chifflier/following{/other_user}","gists_url":"https://api.github.com/users/chifflier/gists{/gist_id}","starred_url":"https://api.github.com/users/chifflier/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chifflier/subscriptions","organizations_url":"https://api.github.com/users/chifflier/orgs","repos_url":"https://api.github.com/users/chifflier/repos","events_url":"https://api.github.com/users/chifflier/events{/privacy}","received_events_url":"https://api.github.com/users/chifflier/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-11-17T09:17:57Z","updated_at":"2016-11-29T07:49:50Z","closed_at":null,"body":"Here's a feature request for a future version: being able to not only generate the parser, but also the serializer (which takes a struct and outputs binary data).\r\nNote that, in the same way functions are required to be able to read/interpret complex data, other functions are likely to be required to write complex data."},"comment":{"url":"https://api.github.com/repos/Geal/nom/issues/comments/263499994","html_url":"https://github.com/Geal/nom/issues/367#issuecomment-263499994","issue_url":"https://api.github.com/repos/Geal/nom/issues/367","id":263499994,"user":{"login":"Geal","id":119296,"avatar_url":"https://avatars.githubusercontent.com/u/119296?v=3","gravatar_id":"","url":"https://api.github.com/users/Geal","html_url":"https://github.com/Geal","followers_url":"https://api.github.com/users/Geal/followers","following_url":"https://api.github.com/users/Geal/following{/other_user}","gists_url":"https://api.github.com/users/Geal/gists{/gist_id}","starred_url":"https://api.github.com/users/Geal/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Geal/subscriptions","organizations_url":"https://api.github.com/users/Geal/orgs","repos_url":"https://api.github.com/users/Geal/repos","events_url":"https://api.github.com/users/Geal/events{/privacy}","received_events_url":"https://api.github.com/users/Geal/received_events","type":"User","site_admin":false},"created_at":"2016-11-29T07:49:50Z","updated_at":"2016-11-29T07:49:50Z","body":"@theduke including a serializer in nom is part of the plan, and I don't think it will be a duplicate of serde. I have used extensively rustc-serialize and serde, and they work well when your data maps easily to your types, but when you need to be more adaptable, you end up writing a lot of code manually (like, try to map enums to JSON).\r\nThere is some room for a flexible serialization library that does not work like serde."}}
{"actor":{"display_login":"Geal"}}