{"comment":{"created_at":"2011-10-11T23:05:12Z","body":"Awesome.  Thanks for your great work in BiwaScheme...I'm using it in a couple of projects and I'm enjoying it.  Your responsiveness is really encouraging. =)","updated_at":"2011-10-11T23:05:12Z","url":"https://api.github.com/repos/yhara/biwascheme/issues/comments/2372489","id":2372489,"user":{"avatar_url":"https://secure.gravatar.com/avatar/761cf136604b599bda41f79400ce6810?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/rpdillon","id":6383,"login":"rpdillon"}},"action":"created","issue":{"number":28,"created_at":"2011-10-11T08:21:46Z","pull_request":{"diff_url":null,"patch_url":null,"html_url":null},"body":"I think it affects more than just list-ref, but bounds checking is broken:\r\n\r\n```\r\nbiwascheme> (list-ref (iota 9) 9)\r\n[BUG] library function `list-ref' returned JavaScript's undefined\r\n```\r\n\r\n```\r\nbiwascheme> (list-ref (iota 9) 11)\r\nd is undefined\r\n```\r\n\r\nIn the most recent version, the error is the same, though the variable is named 'o' instead of 'd'.  These interactions were taken from the interpreter on biwascheme.org.\r\n\r\nIt's pretty clear what's causing this in the implementation -- it's just a case of some edge cases slipping through the implementation (returning x.cdr without checking if it is defined, for example).","comments":2,"title":"'list-ref' implementation bug","updated_at":"2011-10-11T23:05:12Z","url":"https://api.github.com/repos/yhara/biwascheme/issues/28","id":1872636,"assignee":null,"milestone":null,"closed_at":"2011-10-11T14:34:43Z","user":{"avatar_url":"https://secure.gravatar.com/avatar/761cf136604b599bda41f79400ce6810?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/rpdillon","id":6383,"login":"rpdillon"},"html_url":"https://github.com/yhara/biwascheme/issues/28","labels":[],"state":"closed"},"legacy":{"issue_id":1872636,"comment_id":2372489}}