code review 4428064: rpc: allow the argument (first arg of method) to be a v...

rpc: allow the argument (first arg of method) to be a value rather than a pointer.
Can make the API nicer in some cases.

[r, 2011-04-26 00:35:43]

Hello rsc (cc: golang-dev@googlegroups.com),

I'd like you to review this change to
https://go.googlecode.com/hg/

[rsc, 2011-04-26 03:18:19]

LGTM

That's a stunningly bad shortening of the subject
by Rietveld.  (allow the argument to be a v...)

I stared at the code thinking how on earth can the
*first* argument be variadic?

[rog, 2011-04-26 09:37:15]

Why not allow an RPC method to actually return a value rather than passing
in a pointer?
On 26 Apr 2011 04:18, <rsc@golang.org> wrote:
> LGTM
>
> That's a stunningly bad shortening of the subject
> by Rietveld. (allow the argument to be a v...)
>
> I stared at the code thinking how on earth can the
> *first* argument be variadic?
>
>
>
> http://codereview.appspot.com/4428064/

[r2, 2011-04-26 15:30:09]

On Apr 26, 2011, at 2:37 AM, roger peppe wrote:

> Why not allow an RPC method to actually return a value rather than passing in
a pointer?
> 
One step at a time.

-rob

[r, 2011-04-26 22:07:28]

*** Submitted as http://code.google.com/p/go/source/detail?r=574ea59129da ***

rpc: allow the argument (first arg of method) to be a value rather than a
pointer.
Can make the API nicer in some cases.

R=rsc, rog, r2
CC=golang-dev
http://codereview.appspot.com/4428064