Do you consider that to be too complex for the task at hand (ignoring GC issues momentarily)
Conversation
I'm saying that the semantics blocks either introduce the problems I mentioned, or lots of special cases wrt to them
3
and as I said earlier, if the ONLY issue with this code is the use of blocks, they could be replaced with delegates
1
I'll take a look at a delegate based example if you want to make one
1
ok but can you answer if the only issues are GC-related that you have with this?
2
(which btw if THAT produces crazy block results, then basically all blocks in ObjC should be causing crazy memory explosions)
1
objc isn't that dynamic, but my ideal language is
2
thus not allowing for use of blocks basically at all. I would rather have a language with blocks than that feature.
1
not IMO - legit uses of blocks are for collection ops. Blocks for callbacks are a very poor man's coroutines.
1
how would you replace view.drawRectBlock in my example (very much a callback) with a coroutine?
2
Replying to