Big Clodsire with Tiny Balloon @wallhackio@cat.family

@coriander sorry goblin but i also have not been enjoying the heat lately.

@lapis sometimes i feel great FOMO from having not been on tumblr back when it was big

@lapis I actually haven't seen this before lmao

Something really cool about having a physics degree is that I got an A in thermodynamics and I still don't know how a refrigerator works

@lapis this is how i learned about the vivziepop homestuck pilot, which i cannot believe is real

@cam delete this

@cam delete this

PEMDAS! At the Disco

@monorail ....i also thought it was a juice box

quagzilla
https://xcancel.com/enjoiyourcactus/status/1952531298850836505

@cam fuck I wanted to post this! now what do I post!!!!!!

@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_ what is wrong with having an iife that is a procedure can use again?

@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

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

@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.

@aescling @vaporeon_ why are there parenthesis after @lambda _:_()?

@aescling @vaporeon_ what the fuck

@aescling @vaporeon_ how would I do it in python?

@maple i mean, it does look cool though