- All Known Implementing Classes:
- CallManyArgsBlockNode, CallManyArgsBlockPassNode, CallManyArgsNode, CallNoArgBlockNode, CallNoArgBlockPassNode, CallNoArgNode, CallNode, CallOneArgBlockNode, CallOneArgBlockPassNode, CallOneArgFixnumNode, CallOneArgNode, CallSpecialArgBlockNode, CallSpecialArgBlockPassNode, CallSpecialArgNode, CallThreeArgBlockNode, CallThreeArgBlockPassNode, CallThreeArgNode, CallTwoArgBlockNode, CallTwoArgBlockPassNode, CallTwoArgNode, FCallManyArgsBlockNode, FCallManyArgsBlockPassNode, FCallManyArgsNode, FCallNoArgBlockNode, FCallNoArgBlockPassNode, FCallNoArgNode, FCallNode, FCallOneArgBlockNode, FCallOneArgBlockPassNode, FCallOneArgNode, FCallSpecialArgBlockNode, FCallSpecialArgBlockPassNode, FCallSpecialArgNode, FCallThreeArgBlockNode, FCallThreeArgBlockPassNode, FCallThreeArgNode, FCallTwoArgBlockNode, FCallTwoArgBlockPassNode, FCallTwoArgNode, SuperNode, ZSuperNode
public interface BlockAcceptingNode
Any thing which implements this represents a Callable-like node which can have a block
associated with it as part of that call. The calls which can be this are: CallNode, FCallNode,
VCallNode, and SuperNode. Blocks (the IterNode that this interface refers to can be either
an IterNode ( {...} or do ... end ) or a BlockPassNode (&block).
It is likely we can remove this interface once the parser explicitly passes all iters into
the callable node during construction.