Conlang/cl-interpret/Cargo.toml

[package]
name = "cl-interpret"
repository.workspace = true
version.workspace = true
authors.workspace = true
edition.workspace = true
license.workspace = true
publish.workspace = true

[dependencies]
cl-ast = { path = "../cl-ast" }
cl-structures = { path = "../cl-structures" }


[dev-dependencies]
cl-lexer = { path = "../cl-lexer" }
cl-parser = { path = "../cl-parser" }
interpreter: Break out into a separate crate My editor's performance was tanking because of macro interpreter::builtins::builtin! Temporary solution: move the interpreter into a separate crate If I intended to keep the interpreter around, in the long-term, it might be an idea to make a proc-macro for builtin expansion. However, the only reason I need the macros is because the interpreter's dynamic typing implementation is so half-baked. After I bang out the new type checker/inference engine, I'll have to rewrite the entire interpreter anyway! 2024-02-29 23:51:38 +00:00			`[package]`
			`name = "cl-interpret"`
			`repository.workspace = true`
			`version.workspace = true`
			`authors.workspace = true`
			`edition.workspace = true`
			`license.workspace = true`
			`publish.workspace = true`

			`[dependencies]`
cl-ast: Move AST definition into its own crate 2024-03-01 01:49:50 +00:00			`cl-ast = { path = "../cl-ast" }`
			`cl-structures = { path = "../cl-structures" }`
cl-parser: Move parser into its own crate 2024-03-01 02:41:07 +00:00

			`[dev-dependencies]`
cl-lexer: Move lexer into its own crate 2024-03-01 02:58:50 +00:00			`cl-lexer = { path = "../cl-lexer" }`
cl-parser: Move parser into its own crate 2024-03-01 02:41:07 +00:00			`cl-parser = { path = "../cl-parser" }`