{"action":"created","issue":{"url":"https://api.github.com/repos/VinylRecords/Vinyl/issues/55","repository_url":"https://api.github.com/repos/VinylRecords/Vinyl","labels_url":"https://api.github.com/repos/VinylRecords/Vinyl/issues/55/labels{/name}","comments_url":"https://api.github.com/repos/VinylRecords/Vinyl/issues/55/comments","events_url":"https://api.github.com/repos/VinylRecords/Vinyl/issues/55/events","html_url":"https://github.com/VinylRecords/Vinyl/issues/55","id":37529512,"number":55,"title":"Duplicate fields may be present in records","user":{"login":"jonsterling","id":55057,"avatar_url":"https://avatars.githubusercontent.com/u/55057?v=3","gravatar_id":"","url":"https://api.github.com/users/jonsterling","html_url":"https://github.com/jonsterling","followers_url":"https://api.github.com/users/jonsterling/followers","following_url":"https://api.github.com/users/jonsterling/following{/other_user}","gists_url":"https://api.github.com/users/jonsterling/gists{/gist_id}","starred_url":"https://api.github.com/users/jonsterling/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jonsterling/subscriptions","organizations_url":"https://api.github.com/users/jonsterling/orgs","repos_url":"https://api.github.com/users/jonsterling/repos","events_url":"https://api.github.com/users/jonsterling/events{/privacy}","received_events_url":"https://api.github.com/users/jonsterling/received_events","type":"User","site_admin":false},"labels":[{"id":17530069,"url":"https://api.github.com/repos/VinylRecords/Vinyl/labels/bug","name":"bug","color":"fc2929","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2014-07-10T03:42:21Z","updated_at":"2016-12-21T14:52:57Z","closed_at":null,"body":"I'd like to open this issue for discussion, though I do not presently have any thoughts on what the right way to resolve it is.\n\nBasically, the following is a valid record type: `Rec el f [X,X]`; getters & setters will pick the leftmost `X`, but this is still pretty confusing behavior.\n\nWe could change (type-level) `++` and (value-level) `<+>` to coalesce fields in a left-biased way. Is this an improvement? It might be...\n\nClearly the actual defect lies in using the HList-style structure to represent records: the type-theoretic denotation is simply a dependent product over a region of the key space, and this is very well-behaved in ETT. But whilst such a thing is kind of possible in Haskell, it would be very troublesome to express and would lack a number of properties that we want.\n"},"comment":{"url":"https://api.github.com/repos/VinylRecords/Vinyl/issues/comments/268541525","html_url":"https://github.com/VinylRecords/Vinyl/issues/55#issuecomment-268541525","issue_url":"https://api.github.com/repos/VinylRecords/Vinyl/issues/55","id":268541525,"user":{"login":"2426021684","id":16529951,"avatar_url":"https://avatars.githubusercontent.com/u/16529951?v=3","gravatar_id":"","url":"https://api.github.com/users/2426021684","html_url":"https://github.com/2426021684","followers_url":"https://api.github.com/users/2426021684/followers","following_url":"https://api.github.com/users/2426021684/following{/other_user}","gists_url":"https://api.github.com/users/2426021684/gists{/gist_id}","starred_url":"https://api.github.com/users/2426021684/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/2426021684/subscriptions","organizations_url":"https://api.github.com/users/2426021684/orgs","repos_url":"https://api.github.com/users/2426021684/repos","events_url":"https://api.github.com/users/2426021684/events{/privacy}","received_events_url":"https://api.github.com/users/2426021684/received_events","type":"User","site_admin":false},"created_at":"2016-12-21T14:52:57Z","updated_at":"2016-12-21T14:52:57Z","body":"@acowley That would work but in my opinion the type should not be duplicated in the first place."}}
{"actor":{"display_login":"2426021684"}}