{"action":"created","issue":{"url":"https://api.github.com/repos/kframework/k/issues/1945","labels_url":"https://api.github.com/repos/kframework/k/issues/1945/labels{/name}","comments_url":"https://api.github.com/repos/kframework/k/issues/1945/comments","events_url":"https://api.github.com/repos/kframework/k/issues/1945/events","html_url":"https://github.com/kframework/k/issues/1945","id":123406980,"number":1945,"title":"nice error messages","user":{"login":"daejunpark","id":5491770,"avatar_url":"https://avatars.githubusercontent.com/u/5491770?v=3","gravatar_id":"","url":"https://api.github.com/users/daejunpark","html_url":"https://github.com/daejunpark","followers_url":"https://api.github.com/users/daejunpark/followers","following_url":"https://api.github.com/users/daejunpark/following{/other_user}","gists_url":"https://api.github.com/users/daejunpark/gists{/gist_id}","starred_url":"https://api.github.com/users/daejunpark/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/daejunpark/subscriptions","organizations_url":"https://api.github.com/users/daejunpark/orgs","repos_url":"https://api.github.com/users/daejunpark/repos","events_url":"https://api.github.com/users/daejunpark/events{/privacy}","received_events_url":"https://api.github.com/users/daejunpark/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-12-22T03:44:22Z","updated_at":"2015-12-22T21:30:36Z","closed_at":null,"body":"@grosu said:\r\n> Also, in terms of what else to work on, @daejunpark , what is really really needed is to make sure that, once we make the transition, we will not need to look back at 3.6. Otherwise, by definitions, we are not ready to transit. In addition to making the tutorial examples work, which I am 100% sure that we will before the deadline, we also need to make sure that we do not lose any of the nice error messages that we had in 3.6, which we've spent many tens of hours to design. Some of them are unnecessary now, because we do stronger consistency checks on K modules, but many of them are probably still necessary. Without them, users/students will stumble into errors that they have no idea what they mean (e.g., uncaught exceptions). I would say that that is probably the best thing you can really help us with, especially while you travel in Korea. How does this sound? Thanks!\r\n"},"comment":{"url":"https://api.github.com/repos/kframework/k/issues/comments/166734660","html_url":"https://github.com/kframework/k/issues/1945#issuecomment-166734660","issue_url":"https://api.github.com/repos/kframework/k/issues/1945","id":166734660,"user":{"login":"cos","id":37514,"avatar_url":"https://avatars.githubusercontent.com/u/37514?v=3","gravatar_id":"","url":"https://api.github.com/users/cos","html_url":"https://github.com/cos","followers_url":"https://api.github.com/users/cos/followers","following_url":"https://api.github.com/users/cos/following{/other_user}","gists_url":"https://api.github.com/users/cos/gists{/gist_id}","starred_url":"https://api.github.com/users/cos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cos/subscriptions","organizations_url":"https://api.github.com/users/cos/orgs","repos_url":"https://api.github.com/users/cos/repos","events_url":"https://api.github.com/users/cos/events{/privacy}","received_events_url":"https://api.github.com/users/cos/received_events","type":"User","site_admin":false},"created_at":"2015-12-22T21:30:36Z","updated_at":"2015-12-22T21:30:36Z","body":"@daejunpark, your best bet would be to look at instantiations of `KEMException` and figure out what they checked for. If it's not obvious on a first read, do a blame and bug the people who implemented most of that code."}}