1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203
//! Simple interpreter for ASTs produced by [`arithmetic-parser`]. //! //! # How it works //! //! 1. A `Block` of statements is *compiled* into an [`ExecutableModule`]. Internally, //! compilation processes the AST of the block and transforms it into a non-recusrive form. //! An [`ExecutableModule`] may require *imports* (such as [`NativeFn`]s or constant [`Value`]s), //! which can be taken from a [`VariableMap`] (e.g., an [`Environment`]). //! 2. [`ExecutableModule`] can then be executed, for the return value and/or for the //! changes at the top-level variable scope. There are two major variables influencing //! the execution outcome. An [arithmetic](crate::arith) is used to define arithmetic ops //! (`+`, unary and binary `-`, `*`, `/`, `^`) and comparisons (`==`, `!=`, `>`, `<`, `>=`, `<=`). //! Imports may be redefined at this stage as well. //! //! # Type system //! //! [`Value`]s have 4 major types: //! //! - **Numbers** corresponding to literals in the parsed `Block` //! - **Boolean values** //! - **Functions,** which are further subdivided into native functions (defined in the Rust code) //! and interpreted ones (defined within a module) //! - **Tuples / arrays**. //! //! Besides these types, there is an auxiliary one: [`OpaqueRef`], which represents a //! reference-counted native value, which can be returned from native functions or provided to //! them as an arg, but is otherwise opaque from the point of view of the interpreted code //! (cf. `anyref` in WASM). //! //! # Semantics //! //! - All variables are immutable. Re-declaring a var shadows the previous declaration. //! - Functions are first-class (in fact, a function is just a variant of the [`Value`] enum). //! - Functions can capture variables (including other functions). All captures are by value. //! - Arithmetic operations are defined on numbers and tuples. Ops or numbers are defined //! via the [`Arithmetic`]. With tuples, operations are performed per-element. //! Binary operations require tuples of the same size, or a tuple and a primitive value. //! As an example, `(1, 2) + 3` and `(2, 3) / (4, 5)` are valid, but `(1, 2) * (3, 4, 5)` isn't. //! - Methods are considered syntactic sugar for functions, with the method receiver considered //! the first function argument. For example, `(1, 2).map(sin)` is equivalent to //! `map((1, 2), sin)`. //! - Equality comparisons (`==`, `!=`) are defined on all types of values. //! //! - For bool values, the comparisons work as expected. //! - For functions, the equality is determined by the pointer (2 functions are equal //! iff they alias each other). //! - `OpaqueRef`s either use the [`PartialEq`] impl of the underlying type or //! the pointer equality, depending on how the reference was created; see [`OpaqueRef`] docs //! for more details. //! - Equality for numbers is determined by the [`Arithmetic`]. //! - Tuples are equal if they contain the same number of elements and elements are pairwise //! equal. //! - Different types of values are always non-equal. //! //! - Order comparisons (`>`, `<`, `>=`, `<=`) are defined for primitive values only and use //! [`OrdArithmetic`]. //! - No type checks are performed before evaluation. //! - Type annotations are completely ignored. This means that the interpreter may execute //! code that is incorrect with annotations (e.g., assignment of a tuple to a variable which //! is annotated to have a numeric type). //! //! # Crate features //! //! - `std`. Enables support of types from `std`, such as the `Error` trait, and propagates //! to dependencies. Importantly, `std` is necessary for floating-point arithmetics. //! - `complex`. Implements [`Number`] for floating-point complex numbers from //! the [`num-complex`] crate (i.e., `Complex32` and `Complex64`). Enables complex number parsing //! in `arithmetic-parser`. //! - `bigint`. Implements `Number` and a couple of other helpers for big integers //! from the [`num-bigint`] crate (i.e., `BigInt` and `BigUint`). Enables big integer parsing //! in `arithmetic-parser`. //! //! [`Arithmetic`]: crate::arith::Arithmetic //! [`OrdArithmetic`]: crate::arith::OrdArithmetic //! [`arithmetic-parser`]: https://crates.io/crates/arithmetic-parser //! [`num-complex`]: https://crates.io/crates/num-complex //! [`num-bigint`]: https://crates.io/crates/num-bigint //! //! # Examples //! //! ``` //! use arithmetic_parser::grammars::{F32Grammar, Parse, Untyped}; //! use arithmetic_eval::{ //! fns, Assertions, Comparisons, Environment, Prelude, Value, VariableMap, //! }; //! //! # fn main() -> anyhow::Result<()> { //! let program = r#" //! // The interpreter supports all parser features, including //! // function definitions, tuples and blocks. //! order = |x, y| (min(x, y), max(x, y)); //! assert_eq(order(0.5, -1), (-1, 0.5)); //! (_, M) = order(3^2, { x = 3; x + 5 }); //! M //! "#; //! let program = Untyped::<F32Grammar>::parse_statements(program)?; //! //! let mut env = Environment::new(); //! // Add some native functions to the environment. //! env.extend(Prelude.iter()); //! env.extend(Assertions.iter()); //! env.extend(Comparisons.iter()); //! //! // To execute statements, we first compile them into a module. //! let module = env.compile_module("test", &program)?; //! // Then, the module can be run. //! assert_eq!(module.run()?, Value::Number(9.0)); //! # Ok(()) //! # } //! ``` //! //! More complex examples are available in the `examples` directory of the crate. #![cfg_attr(not(feature = "std"), no_std)] #![cfg_attr(docsrs, feature(doc_cfg))] #![doc(html_root_url = "https://docs.rs/arithmetic-eval/0.2.0")] #![warn(missing_docs, missing_debug_implementations)] #![warn(clippy::all, clippy::pedantic)] #![allow( clippy::missing_errors_doc, clippy::must_use_candidate, clippy::module_name_repetitions )] // Polyfill for `alloc` types. mod alloc { #[cfg(not(feature = "std"))] extern crate alloc; #[cfg(not(feature = "std"))] pub use alloc::{ borrow::ToOwned, boxed::Box, format, rc::Rc, string::{String, ToString}, vec, vec::Vec, }; #[cfg(feature = "std")] pub use std::{ borrow::ToOwned, boxed::Box, format, rc::Rc, string::{String, ToString}, vec, vec::Vec, }; } pub use self::{ compiler::CompilerExt, error::{Error, ErrorKind, EvalResult}, executable::{ ExecutableModule, ExecutableModuleBuilder, IndexedId, ModuleId, ModuleImports, WildcardId, WithArithmetic, }, values::{ Assertions, CallContext, Comparisons, Environment, Function, InterpretedFn, NativeFn, OpaqueRef, Prelude, SpannedValue, Value, ValueType, VariableMap, }, }; pub mod arith; mod compiler; pub mod error; mod executable; pub mod fns; mod values; /// Marker trait for possible literals. /// /// This trait is somewhat of a crutch, necessary to ensure that [function wrappers] can accept /// number arguments and distinguish them from other types (booleans, vectors, tuples, etc.). /// /// [function wrappers]: crate::fns::FnWrapper pub trait Number: Clone + 'static {} impl Number for i8 {} impl Number for u8 {} impl Number for i16 {} impl Number for u16 {} impl Number for i32 {} impl Number for u32 {} impl Number for i64 {} impl Number for u64 {} impl Number for i128 {} impl Number for u128 {} impl Number for f32 {} impl Number for f64 {} #[cfg(feature = "num-complex")] impl Number for num_complex::Complex32 {} #[cfg(feature = "num-complex")] impl Number for num_complex::Complex64 {} #[cfg(feature = "num-bigint")] impl Number for num_bigint::BigInt {} #[cfg(feature = "num-bigint")] impl Number for num_bigint::BigUint {}