Is there a way that a function is called and then not return to call site? I have a exit function which does the cleanup and logging.

If an exception is thrown?

Yes but putting the whole code under try catch is little ugly

What are you trying to do, that makes you want to return to not the call site?

You can tell the typesystem you won't return by returning type

Nothing

, but I second that it's not clear what your question is.

@karelpeeters Basically I want to run a piece of code from anywhere and not continue the remaining code from the call site

I don't think methods have enough control over their callers to do that. You'll need to use standard flow control mechanisms to do that (like returning from the calling method after calling the sub-method).

I still don't understand what you mean.

In c++ I used goto at the end of the file.

If you were really dedicated to doing that, you might be able to achieve something similar with coroutines, but I think it would take a lot of work and not be worth it because it would probably require making most of your codebase suspendable. I'm even know if it's possible, but it's the only thing I can think of that might let you do that.

Yeah, what you’re looking for is essentially a goto statement, which Kotlin (or nearly any modern language) does not (and should not) support. The closest a high-level language should ever get to a goto is an exception

I would advise sticking to normal flow control. Oh! If you call

System.exit()

it will kill the process. You could do your logging then end the application. Based on your description of how you were using the original function this might do what you want.

However, if you use some kind of event bus and event-driven architecture, you could post an event in one place, and have the handler cancel the event after cleanup

Thanks for the suggestions

what about launching a coroutine and not waiting for it?