this post was submitted on 02 Jan 2026
92 points (98.9% liked)
Programming
24348 readers
235 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Definitely (being young and recency bias) all the weird stuff happening in the lua engine in the old ComputerCraft versions (1.45ish and 1.75) I'm playing.
I'm not really testing rigorously enough, but it seems to have been in 1.45, which i stopped playing because of other reasons (turtle api too primitive), making a function a() return a function b() that captures one of a's local variables, made it crash.
now on 1.75 it doesn't do that anymore, but now I pass some functions through the output of a coroutine, and they just sometimes turn into nil when I call them the second time. it literally throws "attempt to call nil on line 245" when line 245 is like:
I even printed func before calling it, and it told me it was a function, except earlier, where it told me it was nil. Now I'm going to stop using coroutines and hope the architecture of my program changes enough so the bug goes away.
I'm playing the Direwolf20 season 7 minecraft modpack btw
ok the last one was because i misspelled an identifier and because when you call a function in a table, my stupid lua attributes the problem to the call site and not where the function is defined