Refactor state initialization in the run function for improved clarity and maintainability

Author: DevaanshPathak

techlang/interpreter.py

@@ -8,6 +8,22 @@
 from .system_ops import ProcessOpsHandler
 
 
+def initialize_state(
+    state: InterpreterState,
+    inputs: Optional[List[str]] = None,
+    loaded_files: Optional[Set[str]] = None,
+) -> None:
+    """Initialize an existing InterpreterState for execution.
+
+    The CLI REPL keeps a persistent state object and needs the same baseline
+    initialization that `run()` applies to a fresh state.
+    """
+
+    ProcessOpsHandler.prime_cached_streams(state)
+    state.input_queue = list(inputs or [])
+    state.loaded_files = set(loaded_files or set())
+
+
 def run(code: str, inputs: Optional[List[str]] = None, loaded_files: Optional[Set[str]] = None, base_dir: Optional[str] = None) -> str:
     # Entry point: parse, expand aliases, execute, return output
     if base_dir is None:
@@ -16,9 +32,7 @@ def run(code: str, inputs: Optional[List[str]] = None, loaded_files: Optional[Se
         base_dir = os.path.abspath(base_dir)
 
     state = InterpreterState()
-    ProcessOpsHandler.prime_cached_streams(state)
-    state.input_queue = inputs or []
-    state.loaded_files = loaded_files or set()
+    initialize_state(state, inputs=inputs, loaded_files=loaded_files)
 
     tokens: List[str] = parse(code)