Teach me the:
I don't understand what you are asking.
If you use an interrupt, you can do something when the interrupt happens. When the interrupt is over, the program resumes executing where it was before the interrupt occurred. You can not change that.
What you can do, in the interrupt service routine, is to set a flag.
In loop(), or other functions, you can periodically, check the status of the flag. If it is true, do one thing (maybe return). If it is false, do something else.
Of course, instead of checking a flag, you could check the pin state.
In your program, you could have the switch trigger an interrupt. In the interrupt handler, you can not make the claw stop closing. All you can do is set a flag that says that the claw should stop closing.
In the "close the claw" function, you might have a while loop that is moving the claw in small increments.
With the interrupt method, you'd change that to
while(clawNotFullyClosed && !clawIsToStop)
You's set clawIsToStop to false before this loop, and you'd set it to true in the ISR.
With polling, you'd use
while(clawNotFullyClosed && digitalRead(clawSwitch) != HIGH)
Or LOW, depending on how the switch is wired.
I think that you can see that, in this case, using interrupts buys you nothing. You won't know whether the switch was closed and interrupt has been triggered any sooner than you'd learn that the switch was closed.