Go 1.1 Function Calls
docs.google.com
Go 1.1 Function Calls
1–10 of 34 posts
Re: Go 1.1 Function Calls
#2Russ Cox is a g'damn genius. You can spend hours being fascinated by his code and writing: http://research.swtch.com/
Re: Go 1.1 Function Calls
#3OT: if Google thinks you have an account (based on a cookie I guess) it requires you to login to access this document. So you either need to login or delete the cookie or enable incognito/private mode to access the document.
Why doesn't google treat non-logged in users the same as those w/o an account?
Re: Go 1.1 Function Calls
#4Russ Cox is a g'damn genius. You can spend hours being fascinated by his code and writing: http://research.swtch.com/
Not only that, he's really helpful on the Golang Google group in answering questions to all programmers, new & old. What really hooked me onto Go was both the helpfulness of the Google group as well as the nice people on #gonuts.
Re: Go 1.1 Function Calls
#5Ios disallows dynamic code generation at runtime - what other environments could Go target with these restrictions?
Re: Go 1.1 Function Calls
#6OT: if Google thinks you have an account (based on a cookie I guess) it requires you to login to access this document. So you either need to login or delete the cookie or enable incognito/private mode to access the document. Why doesn't google treat non-logged in users the same as those w/o an account?
No it doesn't. Visit it in an Incognito window if you don't believe me.
It's asking for your password because you apparently do have a Google account and it wants to verify your identity before it lets you access things that are tied to your account.
Re: Go 1.1 Function Calls
#7OT: if Google thinks you have an account (based on a cookie I guess) it requires you to login to access this document. So you either need to login or delete the cookie or enable incognito/private mode to access the document. Why doesn't google treat non-logged in users the same as those w/o an account?
No it doesn't. Visit it in an Incognito window if you don't believe me. It's asking for your password because you apparently do have a Google account and it wants to verify your identity before it lets you access things that are tied to your account.
I don't understand how that's different than what the parent was saying
Re: Go 1.1 Function Calls
#8Ios disallows dynamic code generation at runtime - what other environments could Go target with these restrictions?
RSC's saying that 1.1's new calling convention removed the need for dynamic code generation.
Re: Go 1.1 Function Calls
#9OT: if Google thinks you have an account (based on a cookie I guess) it requires you to login to access this document. So you either need to login or delete the cookie or enable incognito/private mode to access the document. Why doesn't google treat non-logged in users the same as those w/o an account?
> Why doesn't google treat non-logged in users the same as those w/o an account?
I wager what they actually want to do is treat those without an account the same as those who are not logged in, but realize they can't get away with that quite yet. (That is to say, I suspect that they would like to turn away all users without accounts.)
Re: Go 1.1 Function Calls
#10Not much to look at, but you can easily play with bound instance methods like the r.Read example in the doc at the playground: http://play.golang.org/p/lnfidH3usx