9:22:04|3b|when generating code from eq-instruction, should i be looking at the predecessors of the instructions in the 2 branches to determine where they merge againi?
9:41:14|3b|and are there other situations (tagbody?) where an instruction would have multiple predecessors without a corresponding if-like instruction so i could just look at a stack of branches to see which is merging?
15:44:28BikeBy "subject to capture" I meant (block name (f (lambda () (return-from name)))) where F is unknown. <- the dynamic environment doesn't have to be captured there, just the timestamp-like-part, which it already is, like we discussed
15:44:54Bikeas for the catch successors, i see, so it's like the two successors now
15:49:27Bikestill need to pass the dynamic environment to calls, guess it can just be a normal argument...
16:51:05Bike_oh, and tagbody wouldn't need a successor to the end, there's no way to nonlocally enter there (unelss there's a tag at the end, in which case it would have one anyway)