Avoid writing @try @catch @else

[singularitti]

Before v1.8, Julia does not support the try ... catch ... else syntax. So I have to use TryCatch.jl to do that:

function __run!(job::Job)
    # See https://github.com/JuliaLang/julia/issues/21130#issuecomment-288423284
    @try begin
        global result = job.def()
    @catch e
        job.stop_time = now()
        @error "come across `$e` when running!"
        job.status = e isa InterruptException ? INTERRUPTED : FAILED
        return e
    @else
        job.stop_time = now()
        job.status = SUCCEEDED
        return result
    @finally
        job.count += 1
    end
end

After moving the function definition to Thunk, I had the same problem (But since I was using Julia v1.8 to develop, so that was fine):

@try
    global result = thunk.f(thunk.args...; thunk.kwargs...)
@catch e
    setresult!(thunk, e)
    return e
@else
    setresult!(thunk, result)
    return result
end

But I just found out, I could just use finally and some tricks to avoid else (since try statement do not return what was included in finally):

try
    thunk.result = Some(thunk.f(thunk.args...; thunk.kwargs...))
catch e
    thunk.erred = true
    thunk.result = Some(e)
finally
    thunk.evaluated = true
end

If no error is raised, thunk.result will be returned; if erred, thunk.result will catch an error and still be returned. No matter what, thunk.evaluated is set to true.

[singularitti]

So the topmost example could be rewritten as

function __run!(job::Job)
    try
        global result = job.def()
        job.stop_time = now()
        job.status = SUCCEEDED
    catch e
        job.stop_time = now()
        @error "come across `$e` when running!"
        job.status = e isa InterruptException ? INTERRUPTED : FAILED
    finally
        job.count += 1
    end
end

I probably did not use that because it was a three-part statement, where the last two could have erred, and I did not want them to be captured.

[singularitti]

One good thing is that I do not have to define a global variable result to return! Since it is captured by thunk.result anyway.