@wallhackio @vaporeon_ ​

@aescling @vaporeon_ oh because it's calling _some_iffe

the pattern

my_func = decorator(my_func)

where you replace a function with a the return value of another function, is equivalent to

@decorator
def my_func():
print('my_func')


So we could define an decorator iife:

def iife(x):
x()

And use it like so:

@iife
def my_func():
print('my_func')


This is fully equivalent to the disgusting evil hack you just shared.

@wallhackio @vaporeon_ does that mean an IIFE decorator implicitly changes a function to None after its definition

@wallhackio @vaporeon_ holy shit it DOES

@aescling @vaporeon_ personally what i would do is

def iife(func):
    func()
    return func

@iife
my_func():
    print('my_func')

So that the original function still exists

@wallhackio @vaporeon_ that defeats the purrpuss of an IIFE

@aescling @vaporeon_ what is wrong with having an iife that is a procedure can use again?

@wallhackio @vaporeon_ IIFEs do not work that way in javascript

@wallhackio @vaporeon_ the entire point of an IIFE is that you are NOT defining a function meant to be actually reused!

@aescling @vaporeon_ the python syntax forces a new variable to be added to the current scope, something the javascript IIFEs do not do

there is no need to perfectly replicate javascript IIFE behavior because it is impossible

@aescling @vaporeon_ whatever the return value of the decorator is becomes the value of the function you decorated

@wallhackio @vaporeon_ indeed