{"action":"closed","issue":{"url":"https://api.github.com/repos/ItsNickBarry/hyperbolic-canvas/issues/12","repository_url":"https://api.github.com/repos/ItsNickBarry/hyperbolic-canvas","labels_url":"https://api.github.com/repos/ItsNickBarry/hyperbolic-canvas/issues/12/labels{/name}","comments_url":"https://api.github.com/repos/ItsNickBarry/hyperbolic-canvas/issues/12/comments","events_url":"https://api.github.com/repos/ItsNickBarry/hyperbolic-canvas/issues/12/events","html_url":"https://github.com/ItsNickBarry/hyperbolic-canvas/issues/12","id":151781071,"number":12,"title":"Range Error: Maximum Call Stack Size Exceeded in Point.js","user":{"login":"DozenalFTW","id":16109220,"avatar_url":"https://avatars.githubusercontent.com/u/16109220?v=3","gravatar_id":"","url":"https://api.github.com/users/DozenalFTW","html_url":"https://github.com/DozenalFTW","followers_url":"https://api.github.com/users/DozenalFTW/followers","following_url":"https://api.github.com/users/DozenalFTW/following{/other_user}","gists_url":"https://api.github.com/users/DozenalFTW/gists{/gist_id}","starred_url":"https://api.github.com/users/DozenalFTW/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DozenalFTW/subscriptions","organizations_url":"https://api.github.com/users/DozenalFTW/orgs","repos_url":"https://api.github.com/users/DozenalFTW/repos","events_url":"https://api.github.com/users/DozenalFTW/events{/privacy}","received_events_url":"https://api.github.com/users/DozenalFTW/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":14,"created_at":"2016-04-29T02:15:06Z","updated_at":"2016-04-30T00:04:47Z","closed_at":"2016-04-30T00:04:47Z","body":"When I was working on a hyperbolic geometry idea the Point.js script threw an error with a huge call stack, consisting of these three over and over:\r\n```\r\nisIdealPoint.js:256\r\ngetHyperbolicRadiusPoint.js:63\r\ngetEuclideanRadiusPoint.js:42\r\n```\r\nApparently `isIdealPoint` calls `getHyperbolicRadiusPoint` which calls `getEuclideanRadiusPoint` which calls `isIdealPoint`... perhaps, change `isIdealPoint` to not use the other two functions?\r\n\r\n**NOTE**: I'm not sure if this bug even exists or if my version of the library is outdated."}}