{"action":"created","issue":{"url":"https://api.github.com/repos/kvark/mint/issues/4","repository_url":"https://api.github.com/repos/kvark/mint","labels_url":"https://api.github.com/repos/kvark/mint/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/kvark/mint/issues/4/comments","events_url":"https://api.github.com/repos/kvark/mint/issues/4/events","html_url":"https://github.com/kvark/mint/issues/4","id":232079703,"number":4,"title":"Design criteria","user":{"login":"Ralith","id":104558,"avatar_url":"https://avatars1.githubusercontent.com/u/104558?v=3","gravatar_id":"","url":"https://api.github.com/users/Ralith","html_url":"https://github.com/Ralith","followers_url":"https://api.github.com/users/Ralith/followers","following_url":"https://api.github.com/users/Ralith/following{/other_user}","gists_url":"https://api.github.com/users/Ralith/gists{/gist_id}","starred_url":"https://api.github.com/users/Ralith/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Ralith/subscriptions","organizations_url":"https://api.github.com/users/Ralith/orgs","repos_url":"https://api.github.com/users/Ralith/repos","events_url":"https://api.github.com/users/Ralith/events{/privacy}","received_events_url":"https://api.github.com/users/Ralith/received_events","type":"User","site_admin":false},"labels":[{"id":613846381,"url":"https://api.github.com/repos/kvark/mint/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-05-29T18:42:59Z","updated_at":"2017-05-30T18:27:54Z","closed_at":null,"body":"IMO, an interop layer should have the following qualities:\r\n\r\n- Lightweight\r\nThe library should be small, compile quickly, and be easy to understand.\r\n- Zero-cost\r\nAdopting the library should not introduce additional run-time overhead compared to exposing internal types.\r\n- Un-opinionated\r\nNo system to be interoperated with should feel like a second-class citizen. Reasonable differing conventions should have equal degrees of support.\r\n- Safe\r\nThe library should prevent nonsensical or unintended operations."},"comment":{"url":"https://api.github.com/repos/kvark/mint/issues/comments/304966515","html_url":"https://github.com/kvark/mint/issues/4#issuecomment-304966515","issue_url":"https://api.github.com/repos/kvark/mint/issues/4","id":304966515,"user":{"login":"kvark","id":107301,"avatar_url":"https://avatars2.githubusercontent.com/u/107301?v=3","gravatar_id":"","url":"https://api.github.com/users/kvark","html_url":"https://github.com/kvark","followers_url":"https://api.github.com/users/kvark/followers","following_url":"https://api.github.com/users/kvark/following{/other_user}","gists_url":"https://api.github.com/users/kvark/gists{/gist_id}","starred_url":"https://api.github.com/users/kvark/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kvark/subscriptions","organizations_url":"https://api.github.com/users/kvark/orgs","repos_url":"https://api.github.com/users/kvark/repos","events_url":"https://api.github.com/users/kvark/events{/privacy}","received_events_url":"https://api.github.com/users/kvark/received_events","type":"User","site_admin":false},"created_at":"2017-05-30T18:27:54Z","updated_at":"2017-05-30T18:27:54Z","body":"@Ralith once new types are introduced, it's quite difficult to draw the line between what's provided and what's not. E.g. should we implement `Add<Point, Vector>`? If we don't, no other library would be able to do it, hence imposing a permanent ergonomic penalty on using the types directly."}}
{"actor":{"display_login":"kvark"}}