Didnt say to go anywhere, just said that people on .world cant see content from hexbear on lemmy.ml posts shown by those comment counts above even though lemmy.ml federates with hexbear. (hexbear used since its the best example of a large blocked instance that can showcase this well. Could have also used .world, .ml and beehaw and same point stands)
Same logic would apply to .world federating with threads. People on lemmy.dbzer0 for example wont see content from threads on .world posts or communities even if .world federates with threads
Just wanted to put a counterpoint to you saying people would need to deal with it indirectly which isnt true proven by the above. You dont need to strawman it by making it a different point
When the draw function calls itself it yields control to that new function its calling. When that function ends it takes back control and continues doing what it was doing.
This means all of the for loops in all of the functions will execute. Draw(1) will do the for loop and then return as it hits the end of the function (standard behaviour when you reach the end of a function even if theres no return statement). Then draw(2) will do the for loop as it gets back control now that draw(1) is done and then return, etc. all the way up
All parts of a function are recursive, theres no such thing as a non recursive part