Meta: update Rust toolchain

rust-toolchain.toml

@@ -1,2 +1,2 @@
 [toolchain]
-channel = "nightly-2024-07-29"
+channel = "nightly-2024-09-12"

src/assembler/mod.rs

@@ -48,9 +48,10 @@ pub(crate) fn assemble_from_segments(
 	assemble_to_data(segments, source_code, options)?.combine_segments()
 }
 
-/// Runs the assembler, but does not combine data from different segments afterwards. Therefore, the assembler
-/// effectively only runs inside segments. This function might modify the given segments during optimization, and it
-/// returns the assembled segments.
+/// Runs the assembler, but does not combine data from different segments afterwards.
+///
+/// Therefore, the assembler effectively only runs inside segments. This function might modify the given segments during
+/// optimization, and it returns the assembled segments.
 ///
 /// # Errors
 /// Unencodeable instructions will cause errors.

src/assembler/table.rs

@@ -98,6 +98,7 @@ pub enum TwoOperandEntry {
 type Table = HashMap<Mnemonic, EntryOrFirstOperandTable>;
 
 /// The [`ASSEMBLY_TABLE`] static data structure contains mappings from mnemonics and operands to the assembled data.
+///
 /// This data is given in the form of functions executed on a [`crate::segments::Segments`] instance.
 pub static ASSEMBLY_TABLE: LazyLock<Table> = LazyLock::new(|| {
 	let mut table = HashMap::new();

src/brr/dsp.rs

@@ -65,10 +65,12 @@ pub fn apply_precise_treble_boost_filter(samples: &[DecodedSample]) -> Vec<Decod
 	apply_fir_filter(filter, samples)
 }
 
-/// Apply an FIR (finite impulse response) filter of arbitrary lookback to the input samples. The input filter only
-/// provides one half of the filter coefficients; it is mirrored and used for lookahead the same as for lookback. For
-/// example, the third coefficient is both used for `x[i-3]` as well as `x[i+3]` when processing sample number `i`. The
-/// zeroth filter coefficient is applied to the sample `x[i]` itself and not involved in mirroring.
+/// Apply an FIR (finite impulse response) filter of arbitrary lookback to the input samples.
+///
+/// The input filter only provides one half of the filter coefficients; it is mirrored and used for lookahead the same
+/// as for lookback. For example, the third coefficient is both used for `x[i-3]` as well as `x[i+3]` when processing
+/// sample number `i`. The zeroth filter coefficient is applied to the sample `x[i]` itself and not involved in
+/// mirroring.
 #[must_use]
 #[allow(clippy::missing_panics_doc, clippy::range_minus_one)]
 pub fn apply_fir_filter<const lookback: usize>(

src/cli.rs

@@ -14,10 +14,12 @@ use parking_lot::RwLock;
 
 use crate::error::{AssemblyError, ErrorCodes};
 
-/// Interface between the assembler backend and any kind of frontend. There currently are three main frontends: the
-/// spcasm compiler command line program, the spcasm-web website in Wasm, and the sals language server. Each frontend
-/// has different requirements for how the backend should react in various situations, especially error conditions. The
-/// backend passes a reference to the frontend around and calls into it during assembly.
+/// Interface between the assembler backend and any kind of frontend.
+///
+/// There currently are three main frontends: the spcasm compiler command line program, the spcasm-web website in Wasm,
+/// and the sals language server. Each frontend has different requirements for how the backend should react in various
+/// situations, especially error conditions. The backend passes a reference to the frontend around and calls into it
+/// during assembly.
 ///
 /// [`Frontend`] need to additionally implement Send and Sync (since it's used in multi-threaded contexts), and
 /// provide debug output.

src/directive.rs

@@ -22,8 +22,10 @@ use crate::sema::value::{Size, SizedAssemblyTimeValue};
 use crate::sema::{self, AssemblyTimeValue, ProgramElement};
 use crate::{byte_vec_to_string, span_to_string, AssemblyCode, AssemblyError, Segments};
 
-/// An assembly directive, often confusingly referred to as a "macro". spcasm uses the term "macro" to specifically mean
-/// user-defined macros, and "directive" to mean builtin commands (i.e. directives) to the assembler.
+/// An assembly directive, often confusingly referred to as a "macro".
+///
+/// spcasm uses the term "macro" to specifically mean user-defined macros, and "directive" to mean builtin commands
+/// (i.e. directives) to the assembler.
 #[derive(Clone, Debug)]
 pub struct Directive {
 	/// Actual data of the directive.

src/segments.rs

@@ -11,10 +11,12 @@ use crate::assembler::sample_table::SampleTable;
 use crate::directive::DirectiveParameterTable;
 use crate::sema::instruction::MemoryAddress;
 
-/// Handles binary segments and assembler state. The type of data contained within each segment is the generic
-/// parameter; the assembler uses memory values and other analysis passes use other kinds of information per assembled
-/// element. Segments provide the datastructure representation of the segment state that the user can manipulate via
-/// various segment-related directives. Segments also contain other global state which is modified via directives.
+/// Handles binary segments and assembler state.
+///
+/// The type of data contained within each segment is the generic parameter; the assembler uses memory values and other
+/// analysis passes use other kinds of information per assembled element. Segments provide the datastructure
+/// representation of the segment state that the user can manipulate via various segment-related directives. Segments
+/// also contain other global state which is modified via directives.
 #[derive(Debug, Clone)]
 pub struct Segments<Contained> {
 	/// The data segments. These are checked later when being combined into one.

src/sema/addressing_mode.rs

@@ -346,9 +346,11 @@ impl Display for AddressingMode {
 	}
 }
 
-/// The categories of addressing modes. This enum is mainly used for the main assembler lookup table to discern which
-/// opcode to use. It is mostly just a list of the variants of the [`AddressingMode`] sum type, but it also factors out
-/// all register addressing modes separately, as that is very important for opcode generation.
+/// The categories of addressing modes.
+///
+/// This enum is mainly used for the main assembler lookup table to discern which opcode to use. It is mostly just a
+/// list of the variants of the [`AddressingMode`] sum type, but it also factors out all register addressing modes
+/// separately, as that is very important for opcode generation.
 #[derive(Clone, Copy, Debug, Eq, PartialEq, Hash)]
 #[allow(clippy::module_name_repetitions)]
 pub enum AddressingModeCategory {