(Yes, I'll sign my name to this comment ... "downvote away.")
In a case such as this, I strongly believe that you should define new method(s). (Cribs such as Contextual::Return are, in my humble, an absolute disaster.) When I look at a piece of source code ... and please presume that I am unfamiliar with it, because the original author just had an unfortunate encounter with a bread truck ... I need to know with certainty what it is going to do. Each time ... every time ... no exceptions ... no magic.
My professional experience has mostly consisted of walking into blazing-fire situations and being paid to put them out. In so doing, I've learned a lot about why software projects hit the fan. This is one of them. Don't you dare be clever ... please, be stupid-clear. No tricks, no cleverness, no magic. Nothing that might affect “the software that is in front of my eyes” that isn’t “in front of my eyes!” Please. Pretty please.