docs: Rust language section consistency
I found out how to use aspell with a custom dictionary and so ran that on `rust.section.md`. These changes are trivial consistency in spelling and nomenclature.
This commit is contained in:
parent
ac4188fe57
commit
933f117a78
|
@ -426,7 +426,7 @@ you of the correct hash.
|
||||||
* `maturinBuildHook`: use [Maturin](https://github.com/PyO3/maturin)
|
* `maturinBuildHook`: use [Maturin](https://github.com/PyO3/maturin)
|
||||||
to build a Python wheel. Similar to `cargoBuildHook`, the optional
|
to build a Python wheel. Similar to `cargoBuildHook`, the optional
|
||||||
variable `buildAndTestSubdir` can be used to build a crate in a
|
variable `buildAndTestSubdir` can be used to build a crate in a
|
||||||
Cargo workspace. Additional maturin flags can be passed through
|
Cargo workspace. Additional Maturin flags can be passed through
|
||||||
`maturinBuildFlags`.
|
`maturinBuildFlags`.
|
||||||
* `cargoCheckHook`: run tests using Cargo. The build type for checks
|
* `cargoCheckHook`: run tests using Cargo. The build type for checks
|
||||||
can be set using `cargoCheckType`. Additional flags can be passed to
|
can be set using `cargoCheckType`. Additional flags can be passed to
|
||||||
|
@ -447,7 +447,7 @@ dependencies. The build itself is then performed by
|
||||||
|
|
||||||
The following example outlines how the `tokenizers` Python package is
|
The following example outlines how the `tokenizers` Python package is
|
||||||
built. Since the Python package is in the `source/bindings/python`
|
built. Since the Python package is in the `source/bindings/python`
|
||||||
directory of the *tokenizers* project's source archive, we use
|
directory of the `tokenizers` project's source archive, we use
|
||||||
`sourceRoot` to point the tooling to this directory:
|
`sourceRoot` to point the tooling to this directory:
|
||||||
|
|
||||||
```nix
|
```nix
|
||||||
|
@ -729,7 +729,7 @@ with import <nixpkgs> {};
|
||||||
Actually, the overrides introduced in the previous section are more
|
Actually, the overrides introduced in the previous section are more
|
||||||
general. A number of other parameters can be overridden:
|
general. A number of other parameters can be overridden:
|
||||||
|
|
||||||
- The version of rustc used to compile the crate:
|
- The version of `rustc` used to compile the crate:
|
||||||
|
|
||||||
```nix
|
```nix
|
||||||
(hello {}).override { rust = pkgs.rust; };
|
(hello {}).override { rust = pkgs.rust; };
|
||||||
|
@ -742,7 +742,7 @@ general. A number of other parameters can be overridden:
|
||||||
(hello {}).override { release = false; };
|
(hello {}).override { release = false; };
|
||||||
```
|
```
|
||||||
|
|
||||||
- Whether to print the commands sent to rustc when building
|
- Whether to print the commands sent to `rustc` when building
|
||||||
(equivalent to `--verbose` in cargo:
|
(equivalent to `--verbose` in cargo:
|
||||||
|
|
||||||
```nix
|
```nix
|
||||||
|
@ -883,11 +883,11 @@ detailed usage.
|
||||||
|
|
||||||
Fenix is an alternative to `rustup` and can also be used as an overlay.
|
Fenix is an alternative to `rustup` and can also be used as an overlay.
|
||||||
|
|
||||||
Both Oxalica's overlay and fenix better integrate with nix and cache optimizations.
|
Both oxalica's overlay and fenix better integrate with nix and cache optimizations.
|
||||||
Because of this and ergonomics, either of those community projects
|
Because of this and ergonomics, either of those community projects
|
||||||
should be preferred to the Mozilla's Rust overlay (nixpkgs-mozilla).
|
should be preferred to the Mozilla's Rust overlay (`nixpkgs-mozilla`).
|
||||||
|
|
||||||
### How to select a specific rustc and toolchain version {#how-to-select-a-specific-rustc-and-toolchain-version}
|
### How to select a specific `rustc` and toolchain version {#how-to-select-a-specific-rustc-and-toolchain-version}
|
||||||
|
|
||||||
You can consume the oxalica overlay and use it to grab a specific Rust toolchain version.
|
You can consume the oxalica overlay and use it to grab a specific Rust toolchain version.
|
||||||
Here is an example `shell.nix` showing how to grab the current stable toolchain:
|
Here is an example `shell.nix` showing how to grab the current stable toolchain:
|
||||||
|
|
Loading…
Reference in a new issue