return {"result": result}
```

**Note**: This is the recommended way going forward, instead of using `startup` and `shutdown` events.

Read more about it in the new docs: [Advanced User Guide: Lifespan Events](https://fastapi.tiangolo.com/advanced/events/).

### Docs

pkg syscall (darwin-arm64), func GetsockoptInt(int, int, int) (int, error)
pkg syscall (darwin-arm64), func Issetugid() bool
pkg syscall (darwin-arm64), func Kevent(int, []Kevent_t, []Kevent_t, *Timespec) (int, error)
pkg syscall (darwin-arm64), func Kill(int, Signal) error
pkg syscall (darwin-arm64), func Kqueue() (int, error)
pkg syscall (darwin-arm64), func Listen(int, int) error

pkg syscall (netbsd-arm64-cgo), func GetsockoptIPv6MTUInfo(int, int, int) (*IPv6MTUInfo, error)
pkg syscall (netbsd-arm64-cgo), func Issetugid() bool
pkg syscall (netbsd-arm64-cgo), func Kevent(int, []Kevent_t, []Kevent_t, *Timespec) (int, error)
pkg syscall (netbsd-arm64-cgo), func Kill(int, Signal) error
pkg syscall (netbsd-arm64-cgo), func Kqueue() (int, error)

<code>f()</code>, <code>h()</code> (if <code>z</code>
evaluates to false), <code>i()</code>, <code>j()</code>,
<code>&lt;-c</code>, <code>g()</code>, and <code>k()</code>.
However, the order of those events compared to the evaluation
and indexing of <code>x</code> and the evaluation
of <code>y</code> and <code>z</code> is not specified,
except as required lexically. For instance, <code>g</code>