{"issue":{"title":"Default method variable names in interfaces are ugly","user":{"login":"andyarvanitis","id":1289006,"url":"https://api.github.com/users/andyarvanitis","gravatar_id":"4d64900613c24ea2acf7bb00453e8dfa","avatar_url":"https://secure.gravatar.com/avatar/4d64900613c24ea2acf7bb00453e8dfa?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"created_at":"2011-12-27T22:06:23Z","milestone":null,"labels":[],"state":"open","updated_at":"2011-12-27T22:06:23Z","id":2666774,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"closed_at":null,"html_url":"https://github.com/eerolanguage/eero/issues/13","body":"Currently, the compiler generates ugly default variable names in interfaces (not in implementations). For example:\r\n{{{\r\ninterface MyClass\r\n   setObject id, withObject id  // generates var names \"objectA\", \"objectB\"\r\nend\r\n}}}\r\n This was done avoid compiler warnings in interfaces for multiple parameters with the same name. The problem with these names occurs when the compiler emits other errors or warnings and references these names. At the very least, the first occurrence should not have any suffix (e.g. \"object\", \"objectA\").","number":13,"url":"https://api.github.com/repos/eerolanguage/eero/issues/13","comments":0,"assignee":null},"action":"opened"}