« Return to Thread: Re: [scala-user] Problem with default arguments and multiple method signatures

Re: [scala-user] Problem with default arguments and multiple method signatures

by Lukas Rytz :: Rate this Message:

On Tue, Jun 2, 2009 at 14:43, James Iry <jamesiry@...> wrote:

Would it be feasible to mangle the getter's name using the parameter types of the overloaded methods?

def foo(x : T1 = xdef, y : T2 = ydef)
def foo(z : T3 = zdef, zz : T4 = zzdef)

def foo$T1$T2$defaul1 = xdef
def foo$T1$T2$defaul2 = ydef
def foo$T3$T4$default1 = zdef
def foo$T3$T4$default2 = zzdef

That would probably work, except that for some types it's not obvious
how to convert them into a name:

def foo(x: { def bar(): Int } = new { def bar() = 1 })
def foo(x: String = "uh")

What do people think, is it too much limitation if we restrict defaults
to one overloaded alternative? After all, defaults often allow you to get
rid of overloads.

Lukas

« Return to Thread: Re: [scala-user] Problem with default arguments and multiple method signatures