blitzar 4.6.1

High-Level Rust wrapper for the blitzar-sys crate
Documentation
Responsible for initializing the C++ commitment backend.

This function initializes the backend so that computations
can proceed either in the CPU or in the GPU. It is only called once. The backend
type must be specified during `build` time using the following flags:

```text
cargo build --features pip-cpu # only the Pippenger commitment CPU is used
cargo build --features naive-gpu # only the naive commitment GPU is used
cargo build --features naive-cpu # only the naive commitment CPU is used
```

Once the backend is initialized, it is not possible to change to
another one. Therefore, if the GPU feature is specified during build time,
then it is not possible to use the CPU to do the computations. 
In the case, no feature is specified during build time, 
the backend will initialize with the pip-cpu as default.

Also, any `compute` function will call this `init_backend`
securing that the backend is always in a proper state.
 
Finally, to guarantee that the code inside this function is not
initialized multiple times, we use the `std::sync::Once` scheme.

# Panics

If the backend initialization fails.