{"action":"created","issue":{"url":"https://api.github.com/repos/ddugovic/Stockfish/issues/103","repository_url":"https://api.github.com/repos/ddugovic/Stockfish","labels_url":"https://api.github.com/repos/ddugovic/Stockfish/issues/103/labels{/name}","comments_url":"https://api.github.com/repos/ddugovic/Stockfish/issues/103/comments","events_url":"https://api.github.com/repos/ddugovic/Stockfish/issues/103/events","html_url":"https://github.com/ddugovic/Stockfish/issues/103","id":187048064,"number":103,"title":"Move no longer fits in 16 bits for crazyhouse (as expected by TT code)","user":{"login":"sf-x","id":6150861,"avatar_url":"https://avatars.githubusercontent.com/u/6150861?v=3","gravatar_id":"","url":"https://api.github.com/users/sf-x","html_url":"https://github.com/sf-x","followers_url":"https://api.github.com/users/sf-x/followers","following_url":"https://api.github.com/users/sf-x/following{/other_user}","gists_url":"https://api.github.com/users/sf-x/gists{/gist_id}","starred_url":"https://api.github.com/users/sf-x/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sf-x/subscriptions","organizations_url":"https://api.github.com/users/sf-x/orgs","repos_url":"https://api.github.com/users/sf-x/repos","events_url":"https://api.github.com/users/sf-x/events{/privacy}","received_events_url":"https://api.github.com/users/sf-x/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":11,"created_at":"2016-11-03T12:36:30Z","updated_at":"2016-11-06T19:44:57Z","closed_at":null,"body":"subj. See definition of `struct TTentry`. Do drops really need extension of `Move` to 18 bits?"},"comment":{"url":"https://api.github.com/repos/ddugovic/Stockfish/issues/comments/258704991","html_url":"https://github.com/ddugovic/Stockfish/issues/103#issuecomment-258704991","issue_url":"https://api.github.com/repos/ddugovic/Stockfish/issues/103","id":258704991,"user":{"login":"ddugovic","id":1834123,"avatar_url":"https://avatars.githubusercontent.com/u/1834123?v=3","gravatar_id":"","url":"https://api.github.com/users/ddugovic","html_url":"https://github.com/ddugovic","followers_url":"https://api.github.com/users/ddugovic/followers","following_url":"https://api.github.com/users/ddugovic/following{/other_user}","gists_url":"https://api.github.com/users/ddugovic/gists{/gist_id}","starred_url":"https://api.github.com/users/ddugovic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ddugovic/subscriptions","organizations_url":"https://api.github.com/users/ddugovic/orgs","repos_url":"https://api.github.com/users/ddugovic/repos","events_url":"https://api.github.com/users/ddugovic/events{/privacy}","received_events_url":"https://api.github.com/users/ddugovic/received_events","type":"User","site_admin":false},"created_at":"2016-11-06T19:44:57Z","updated_at":"2016-11-06T19:44:57Z","body":"I think @isaacl has a point; combining two move types such as `ENPASSANT` and `CASTLING` together somehow could free up an entire `MoveType` for drops, which could be a good thing.\r\n\r\n(Alternatively, we'd encode piece drops using `PROMOTION` and pawn drops some other way, but this seriously drifts from a clean implementation.)"}}
{"actor":{"display_login":"ddugovic"}}