nostr:npub1gcl7nsg5gjejquna9kv3j4kzujhgpakkmmt9ful3772rw4s0xzxqqlcs78 but how would you capture the loop variable if you couldn't know that your closure evaluated its signature line at definition time
nostr:npub1pfe56vzppw077dd04ycr8mx72dqdk0m95ccdfu2j9ak3n7m89nrsf9e2dm yeeeeep https://go.dev/play/p/HFrHlaWpONm
although python's worst feature in my mind is "default args at define time"
Discussion
nostr:npub1gcl7nsg5gjejquna9kv3j4kzujhgpakkmmt9ful3772rw4s0xzxqqlcs78 (if it is not clear, I am agreeing with you, but they're kind of the _same_ bug)