# What ❔

Bump the rust toolchain, dependencies and CUDA version in CI.

# What ❔

Prepares 0.1.0 release (already on crates.io)

⚠️ Changes the build script for cudart to use
[`OUT_DIR`](https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-build-scripts),
since it's an idiomatic approach and breaking it [may have unexpected
results](rust-lang/cargo#5073).

## Why ❔

Releasing on crates.io

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `cargo fmt` and checked with `cargo
check` for any errors or warnings.

# What ❔

This PR re-implements the build process, introducing following features
and changes:
- on the fly CUDA binding creation is removed, a separate bindings
generator binary that can be used to re-create bindings on demand is
implemented
- a configuration flag `no_cuda` is implemented to allow code
compilation and linking without the presence of a CUDA toolkit
installation by replacing the CUDA API calls with stubs.
- crate naming is consolidated and crate versions are bumped to `0.2.0`

## Why ❔

- on the fly bindings creation is potentially brittle, future changes to
the CUDA API can cause compilation errors on the rust side
- compiling and executing non-GPU part of the codebase is desired to
enable development work in environments where CUDA toolkit is not
installed.

## Checklist

- [x] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [x] Code has been formatted via `cargo fmt` and `cargo clippy`.

# What ❔

<!-- What are the changes this PR brings about? -->
<!-- Example: This PR adds a PR template to the repo. -->
<!-- (For bigger PRs adding more context is appreciated) -->

## Why ❔

<!-- Why are these changes done? What goal do they contribute to? What
are the principles behind them? -->
<!-- Example: PR templates ensure PR reviewers, observers, and future
iterators are in context about the evolution of repos. -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `cargo fmt` and checked with `cargo
check` for any errors or warnings.