{"action":"created","issue":{"url":"https://api.github.com/repos/WebAssembly/design/issues/688","repository_url":"https://api.github.com/repos/WebAssembly/design","labels_url":"https://api.github.com/repos/WebAssembly/design/issues/688/labels{/name}","comments_url":"https://api.github.com/repos/WebAssembly/design/issues/688/comments","events_url":"https://api.github.com/repos/WebAssembly/design/issues/688/events","html_url":"https://github.com/WebAssembly/design/issues/688","id":154527176,"number":688,"title":"Opcode Expansion Plans?","user":{"login":"BSalita","id":1225749,"avatar_url":"https://avatars.githubusercontent.com/u/1225749?v=3","gravatar_id":"","url":"https://api.github.com/users/BSalita","html_url":"https://github.com/BSalita","followers_url":"https://api.github.com/users/BSalita/followers","following_url":"https://api.github.com/users/BSalita/following{/other_user}","gists_url":"https://api.github.com/users/BSalita/gists{/gist_id}","starred_url":"https://api.github.com/users/BSalita/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/BSalita/subscriptions","organizations_url":"https://api.github.com/users/BSalita/orgs","repos_url":"https://api.github.com/users/BSalita/repos","events_url":"https://api.github.com/users/BSalita/events{/privacy}","received_events_url":"https://api.github.com/users/BSalita/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-05-12T16:35:04Z","updated_at":"2016-05-14T17:36:10Z","closed_at":"2016-05-14T17:36:10Z","body":"Are there plans for how new opcodes will be implemented? I'm sure new opcodes will be added after V1. The most obvious way to implement new opcode ranges is to specify one or more opcode bytes that signal a 2nd byte range follows."},"comment":{"url":"https://api.github.com/repos/WebAssembly/design/issues/comments/219233102","html_url":"https://github.com/WebAssembly/design/issues/688#issuecomment-219233102","issue_url":"https://api.github.com/repos/WebAssembly/design/issues/688","id":219233102,"user":{"login":"jfbastien","id":298127,"avatar_url":"https://avatars.githubusercontent.com/u/298127?v=3","gravatar_id":"","url":"https://api.github.com/users/jfbastien","html_url":"https://github.com/jfbastien","followers_url":"https://api.github.com/users/jfbastien/followers","following_url":"https://api.github.com/users/jfbastien/following{/other_user}","gists_url":"https://api.github.com/users/jfbastien/gists{/gist_id}","starred_url":"https://api.github.com/users/jfbastien/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jfbastien/subscriptions","organizations_url":"https://api.github.com/users/jfbastien/orgs","repos_url":"https://api.github.com/users/jfbastien/repos","events_url":"https://api.github.com/users/jfbastien/events{/privacy}","received_events_url":"https://api.github.com/users/jfbastien/received_events","type":"User","site_admin":false},"created_at":"2016-05-14T17:36:10Z","updated_at":"2016-05-14T17:36:10Z","body":"Yes, the binary format is still changing but before MVP we intend to have an opcode table so each .wasm defines its own numbering. We'll likely use LEB128 for opcodes, so no need for any more extension scheme.\r\n\r\nFF already has the SIMD opcodes supported, which pushes it past single-bytes.\r\n\r\nClosing for now, feel free to reopen if that doesn't address questions."}}