Skip to content

Commit 4104333

Browse files
committed
remove the ExecutionPackage, byproduct from another system
1 parent d9cc954 commit 4104333

File tree

3 files changed

+5
-195
lines changed

3 files changed

+5
-195
lines changed

README.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -178,12 +178,11 @@ go-polyscript is structured around a few key concepts:
178178
1. **Loader**: Loads script content from various sources (files, strings, http, etc.)
179179
2. **Compiler**: Validates and compiles scripts into internal "bytecode"
180180
3. **ExecutableUnit**: Represents a compiled script ready for execution
181-
4. **ExecutionPackage**: Contains an **ExecutableUnit** and other metadata
182-
5. **Evaluator**: Executes compiled scripts with provided input data
183-
6. **EvalDataPreparer**: Prepares data for evaluation (can be separated from evaluation)
184-
7. **Provider**: Supplies data to scripts during evaluation
185-
8. **Machine**: A specific implementation of a scripting engine (Risor, Starlark, Extism)
186-
9. **EvaluatorResponse**: The response object returned from all **Machine**s
181+
4. **Evaluator**: Executes compiled scripts with provided input data
182+
5. **EvalDataPreparer**: Prepares data for evaluation (can be separated from evaluation)
183+
6. **Provider**: Supplies data to scripts during evaluation
184+
7. **Machine**: A specific implementation of a scripting engine (Risor, Starlark, Extism)
185+
8. **EvaluatorResponse**: The response object returned from all **Machine**s
187186

188187
### Note on Data Access Patterns
189188

engine/executionPackage.go

Lines changed: 0 additions & 62 deletions
This file was deleted.

engine/executionPackage_test.go

Lines changed: 0 additions & 127 deletions
This file was deleted.

0 commit comments

Comments
 (0)