Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to defer functions, closes #403 #431

Merged
merged 2 commits into from
May 24, 2021
Merged

Ability to defer functions, closes #403 #431

merged 2 commits into from
May 24, 2021

Conversation

odino
Copy link
Collaborator

@odino odino commented May 13, 2021

Sometimes it is very helpful to guarantee a certain function is executed
regardless of what code path we take: you can use the defer keyword for
this.

echo(1)
defer echo(3)
echo(2)

When you schedule a function to be deferred, it will executed right at
the end of the current scope. A defer inside a function will then
execute at the end of that function itself:

echo(1)
f fn() {
    defer echo(3)
    echo(2)
}
fn()
echo(4)

You can defer any callable: a function call, a method or even a system
command. This can be very helpful if you need to run a cleanup function
right before wrapping up with your code:

defer `rm my-file.txt`
"some text" > "my-file.txt"

...
...
"some other text" >> "my-file.txt"

In this case, you will be guaranteed to execute the command that removes
my-file.txt before the program closes.

Be aware that code that is deferred does not have access to the return value
of its scope, and will supress errors -- if a defer block messes up you're
not going to see any error. This behavior is experimental, but we would most
likely like to give this kind of control through try...catch...finally.

odino added 2 commits May 13, 2021 21:38
Sometimes it is very helpful to guarantee a certain function is executed
regardless of what code path we take: you can use the `defer` keyword for
this.

```py
echo(1)
defer echo(3)
echo(2)
```

When you schedule a function to be deferred, it will executed right at
the end of the current scope. A `defer` inside a function will then
execute at the end of that function itself:

```py
echo(1)
f fn() {
    defer echo(3)
    echo(2)
}
fn()
echo(4)
```

You can `defer` any callable: a function call, a method or even a system
command. This can be very helpful if you need to run a cleanup function
right before wrapping up with your code:

```sh
defer `rm my-file.txt`
"some text" > "my-file.txt"

...
...
"some other text" >> "my-file.txt"
```

In this case, you will be guaranteed to execute the command that removes
`my-file.txt` before the program closes.

Be aware that code that is deferred does not have access to the return value
of its scope, and will supress errors -- if a `defer` block messes up you're
not going to see any error. This behavior is experimental, but we would most
likely like to give this kind of control through [try...catch...finally](#118).
@odino odino merged commit 789fa09 into 2.6.x May 24, 2021
@odino odino added this to the 2.6.x milestone May 24, 2021
@odino odino mentioned this pull request Sep 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant