{"action":"created","issue":{"url":"https://api.github.com/repos/sq/JSIL/issues/697","labels_url":"https://api.github.com/repos/sq/JSIL/issues/697/labels{/name}","comments_url":"https://api.github.com/repos/sq/JSIL/issues/697/comments","events_url":"https://api.github.com/repos/sq/JSIL/issues/697/events","html_url":"https://github.com/sq/JSIL/issues/697","id":59547452,"number":697,"title":"Accessing members of Tuple<> results in \"undefined\" values","user":{"login":"dbh1997","id":10538969,"avatar_url":"https://avatars.githubusercontent.com/u/10538969?v=3","gravatar_id":"","url":"https://api.github.com/users/dbh1997","html_url":"https://github.com/dbh1997","followers_url":"https://api.github.com/users/dbh1997/followers","following_url":"https://api.github.com/users/dbh1997/following{/other_user}","gists_url":"https://api.github.com/users/dbh1997/gists{/gist_id}","starred_url":"https://api.github.com/users/dbh1997/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dbh1997/subscriptions","organizations_url":"https://api.github.com/users/dbh1997/orgs","repos_url":"https://api.github.com/users/dbh1997/repos","events_url":"https://api.github.com/users/dbh1997/events{/privacy}","received_events_url":"https://api.github.com/users/dbh1997/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/sq/JSIL/labels/Missing%20Feature","name":"Missing Feature","color":"02d7e1"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-03-02T20:48:10Z","updated_at":"2015-03-03T15:21:37Z","closed_at":null,"body":"            var edgeIndexes = new Tuple<int, string>(4, \"67\");\r\n            Console.WriteLine(edgeIndexes.Item1);\r\n            Console.WriteLine(edgeIndexes.Item2);\r\n\r\nresults in:\r\n\r\nundefined\r\nundefined\r\n\r\nI'm looking for an alternative to help performance of functions that contain more than \"one\" out parameter.  The thought was to return a Tuple<> and pick off the members on the calling side.  The alternative of providing a small collection class for each combination is doable, but a bit tedious.\r\n"},"comment":{"url":"https://api.github.com/repos/sq/JSIL/issues/comments/76965219","html_url":"https://github.com/sq/JSIL/issues/697#issuecomment-76965219","issue_url":"https://api.github.com/repos/sq/JSIL/issues/697","id":76965219,"user":{"login":"dbh1997","id":10538969,"avatar_url":"https://avatars.githubusercontent.com/u/10538969?v=3","gravatar_id":"","url":"https://api.github.com/users/dbh1997","html_url":"https://github.com/dbh1997","followers_url":"https://api.github.com/users/dbh1997/followers","following_url":"https://api.github.com/users/dbh1997/following{/other_user}","gists_url":"https://api.github.com/users/dbh1997/gists{/gist_id}","starred_url":"https://api.github.com/users/dbh1997/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dbh1997/subscriptions","organizations_url":"https://api.github.com/users/dbh1997/orgs","repos_url":"https://api.github.com/users/dbh1997/repos","events_url":"https://api.github.com/users/dbh1997/events{/privacy}","received_events_url":"https://api.github.com/users/dbh1997/received_events","type":"User","site_admin":false},"created_at":"2015-03-03T15:21:37Z","updated_at":"2015-03-03T15:21:37Z","body":"Best I can tell, the return type has to be object, and then the calling side would have to use reflection to pick off the pieces by name.  This would make the C# code slower (which we still have to use in our mobile apps), and I don't think it's supported in your translator - nor would I ever expect it to be possible.  I've already had to remove any instance of FieldInfo and MethodInfo and re-write this sections as big switch statements.\r\n\r\nSomebody else suggested that I try making a template class with 2 types, and another with 3 to simulate the Tuple.  Would you expect this work?"}}