Disallow assignment to method, function or class

[JukkaL]

Do not allow assignments to methods, functions or classes.

Update: Note that variables with callable types are still fine.

[Varriount]

Wait, does this mean that operations such as x = func would be disallowed?

[JukkaL]

This does not affect variables or data attributes with callable types. So this will still be valid:

class A:
    def f(self): ...
    g = f # ok
def f(): ...
g = f # ok
g = lambda: ...  # ok as well

However, these will be disallowed (names defined using def or class are basically constants, by default):

def f(): ...
f = ... # not ok
class A:
    def f(self): ...
    f = ... # not ok

[JukkaL]

The restriction allows significantly more efficient code to be generated (inlining etc.). Also updated the issue description to be more clear.

[JukkaL]

It's possible to use a decorator to make a function redefinable. For example (for suitable mutable):

@mutable
void func(): 
    print(1)

func() # 1
func = lambda: print(2)  # ok
func() # 2

(Of course, I assume that function decorators have been implemented.)

I'm not sure whether the above is a good idea yet, but at least it's an option.

The above may be cleaner that this alternative:

void _func():
    print(1)
func = _func  # this can be assigned to, since it's a variable

[frgomes]

hi

Why not @OverRide instead when you ... well.... override it?
Any similarity with Java is not a mere coincidence.

Richard Gomes
http://rgomes.info

On 07/02/13 17:10, Jukka Lehtosalo wrote:

It's possible to use a decorator to make a function redefinable. For
example (for suitable |mutable|):

|@mutable
void func():
print(1)

func() # 1
func = lambda: print(2) # ok
func() # 2
|

(Of course, I assume that function decorators have been implemented.)

I'm not sure whether the above is a good idea yet, but at least it's
an option.

The above may be cleaner that this alternative:

|void _func():
print(1)
func = _func # this can be assigned to, since it's a variable
|

—
Reply to this email directly or view it on GitHub
#119 (comment).

[JukkaL]

frgomes: The mutable name may not be the best one, but I'm not sure about Override either. 'Override' usually refers to method overriding, whereas the original example is something else (though somewhat related). One of the more common uses for 'mutable' functions is probably monkey-patching, so maybe it should be @patchable or @patch...