{"action":"closed","issue":{"url":"https://api.github.com/repos/cmdrkotori/mpc-qt/issues/80","repository_url":"https://api.github.com/repos/cmdrkotori/mpc-qt","labels_url":"https://api.github.com/repos/cmdrkotori/mpc-qt/issues/80/labels{/name}","comments_url":"https://api.github.com/repos/cmdrkotori/mpc-qt/issues/80/comments","events_url":"https://api.github.com/repos/cmdrkotori/mpc-qt/issues/80/events","html_url":"https://github.com/cmdrkotori/mpc-qt/issues/80","id":222853734,"number":80,"title":"[suggestion] use clazy to check for \"inefficient Qt coding mistakes\"","user":{"login":"ahjolinna","id":6993072,"avatar_url":"https://avatars1.githubusercontent.com/u/6993072?v=3","gravatar_id":"","url":"https://api.github.com/users/ahjolinna","html_url":"https://github.com/ahjolinna","followers_url":"https://api.github.com/users/ahjolinna/followers","following_url":"https://api.github.com/users/ahjolinna/following{/other_user}","gists_url":"https://api.github.com/users/ahjolinna/gists{/gist_id}","starred_url":"https://api.github.com/users/ahjolinna/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ahjolinna/subscriptions","organizations_url":"https://api.github.com/users/ahjolinna/orgs","repos_url":"https://api.github.com/users/ahjolinna/repos","events_url":"https://api.github.com/users/ahjolinna/events{/privacy}","received_events_url":"https://api.github.com/users/ahjolinna/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2017-04-19T19:59:03Z","updated_at":"2017-04-20T04:53:49Z","closed_at":"2017-04-20T04:53:49Z","body":"I saw the phoronix news about the new tool from KDE team that checks the Qt code quality, I was thinking this would be useful for mpc-qt also, as clazy isn't for KDE usage only it's for all Qt projects...:\r\n\r\n> Clazy is a Clang-based static analyzer for Qt that can warn about unnecessary memory allocations, poor API decisions, inefficient usage of some API calls, and more. Additional checks are still being added to Clazy.\r\n> \r\n> Qt developers wishing to learn more can find out all of the details via this [KDAB blog post](https://www.kdab.com/uncovering-32-qt-best-practices-compile-time-clazy/). The code checker is available via the[ KDE Git repository.](https://github.com/KDE/clazy)\r\n\r\n---source [phoronix](http://phoronix.com/scan.php?page=news_item&px=Clang-Clazy-Qt-Slow-Mistakes)\r\n"}}
{"actor":{"display_login":"cmdrkotori"}}