{"action":"created","issue":{"url":"https://api.github.com/repos/uwhpsc-2016/homework2/issues/22","repository_url":"https://api.github.com/repos/uwhpsc-2016/homework2","labels_url":"https://api.github.com/repos/uwhpsc-2016/homework2/issues/22/labels{/name}","comments_url":"https://api.github.com/repos/uwhpsc-2016/homework2/issues/22/comments","events_url":"https://api.github.com/repos/uwhpsc-2016/homework2/issues/22/events","html_url":"https://github.com/uwhpsc-2016/homework2/issues/22","id":151710870,"number":22,"title":"Preallocated `out` in wrappers.py","user":{"login":"alyfarahat","id":18155486,"avatar_url":"https://avatars.githubusercontent.com/u/18155486?v=3","gravatar_id":"","url":"https://api.github.com/users/alyfarahat","html_url":"https://github.com/alyfarahat","followers_url":"https://api.github.com/users/alyfarahat/followers","following_url":"https://api.github.com/users/alyfarahat/following{/other_user}","gists_url":"https://api.github.com/users/alyfarahat/gists{/gist_id}","starred_url":"https://api.github.com/users/alyfarahat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alyfarahat/subscriptions","organizations_url":"https://api.github.com/users/alyfarahat/orgs","repos_url":"https://api.github.com/users/alyfarahat/repos","events_url":"https://api.github.com/users/alyfarahat/events{/privacy}","received_events_url":"https://api.github.com/users/alyfarahat/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/uwhpsc-2016/homework2/labels/Answered","name":"Answered","color":"c2e0c6"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2016-04-28T18:25:09Z","updated_at":"2016-04-29T23:51:21Z","closed_at":null,"body":"Throughout wrappers.py, the pattern is to locally allocate `out` using `empty_like()` and then return it. I am not sure, but could that create an issue since unit tests are accessing `out` outside the function scope, with a chance that `out` could be automatically garbage collected at return time (since this is Python and not C). ?"},"comment":{"url":"https://api.github.com/repos/uwhpsc-2016/homework2/issues/comments/215909581","html_url":"https://github.com/uwhpsc-2016/homework2/issues/22#issuecomment-215909581","issue_url":"https://api.github.com/repos/uwhpsc-2016/homework2/issues/22","id":215909581,"user":{"login":"alyfarahat","id":18155486,"avatar_url":"https://avatars.githubusercontent.com/u/18155486?v=3","gravatar_id":"","url":"https://api.github.com/users/alyfarahat","html_url":"https://github.com/alyfarahat","followers_url":"https://api.github.com/users/alyfarahat/followers","following_url":"https://api.github.com/users/alyfarahat/following{/other_user}","gists_url":"https://api.github.com/users/alyfarahat/gists{/gist_id}","starred_url":"https://api.github.com/users/alyfarahat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alyfarahat/subscriptions","organizations_url":"https://api.github.com/users/alyfarahat/orgs","repos_url":"https://api.github.com/users/alyfarahat/repos","events_url":"https://api.github.com/users/alyfarahat/events{/privacy}","received_events_url":"https://api.github.com/users/alyfarahat/received_events","type":"User","site_admin":false},"created_at":"2016-04-29T23:51:21Z","updated_at":"2016-04-29T23:51:21Z","body":"All my test cases were non-singular (non-zero diagonal elements). It could be a compiler version issue. Some compilers will translate the for-loop literally; in this case the loop should never terminate. Others will do some loop-optimization that will compile into different semantics: in which case the loop shall terminate. Since the issue is an obvious bug, I am definitely not blaming the compiler. I am just trying to understand how come the same code works on the same test case on one computer while it does not on another."}}