Compare commits

..

No commits in common. "162b748d3e546d9a6adf0f4db31a35ff736e1394" and "a66ed69e256fba15cd981bf878ac598343c75f10" have entirely different histories.

5 changed files with 4 additions and 27 deletions

View File

@ -4,7 +4,6 @@ version = "0.1.0"
edition = "2024"
[dependencies]
rush_macro = { path = "rush_macro" }
rand = "0.9.0"
paste = "1.0.15"
rust_decimal = { version = "1.37", features = ["macros", "maths"] }

View File

@ -1,13 +0,0 @@
[package]
name = "rush_macro"
version = "0.1.0"
edition = "2024"
# wait to add this until later bc Rust errors
# until it works.
#[lib]
#proc-macro = true
[dependencies]
syn = { version = "2.0.100" } # rust code from string -> data structure
quote = { version = "1.0.40" } # syn data structures to rust code

View File

@ -1,9 +0,0 @@
#[cfg(test)]
mod tests {
use super::*;
#[test]
fn it_works() {
assert_eq!(true, true);
}
}

View File

@ -275,7 +275,7 @@ pub mod vector;
// unsure how to procedurally read a file and put all functions
// into a vector. Probably need to use procedural macros, but I'm not there yet.
/*pub fn int_instructions() -> Vec<fn(&mut PushState)> {
pub fn int_instructions() -> Vec<fn(&mut PushState)> {
vec![
// numeric.rs
int_add,
@ -657,4 +657,4 @@ pub fn code_instructions() -> Vec<fn(&mut PushState)> {
code_from_vector_char,
code_from_exec,
]
}*/
}

View File

@ -7,7 +7,7 @@ mod push;
fn main() {
// These need to stay so linter doesn't go crazy.
/* int_instructions();
int_instructions();
float_instructions();
string_instructions();
boolean_instructions();
@ -18,7 +18,7 @@ fn main() {
vector_boolean_instructions();
vector_char_instructions();
exec_instructions();
code_instructions();*/
code_instructions();
let mut empty_state = EMPTY_STATE;
interpret_program(&mut empty_state, 1000, 1000);
}