From 36d22d82aa202bb199967e9512281e9a53db42c9 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 21:33:14 +0200 Subject: Adding upstream version 115.7.0esr. Signed-off-by: Daniel Baumann --- third_party/rust/jsparagus-scope/src/lib.rs | 36 +++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 third_party/rust/jsparagus-scope/src/lib.rs (limited to 'third_party/rust/jsparagus-scope/src/lib.rs') diff --git a/third_party/rust/jsparagus-scope/src/lib.rs b/third_party/rust/jsparagus-scope/src/lib.rs new file mode 100644 index 0000000000..919776ee38 --- /dev/null +++ b/third_party/rust/jsparagus-scope/src/lib.rs @@ -0,0 +1,36 @@ +//! Collect information about scopes and bindings, used by the emitter. +//! +//! Scope analysis happens in a separate pass after the AST is built: +//! +//! 1. Parse the script, check for early errors, and build an AST. +//! 2. Traverse the AST and do scope analysis (this crate). +//! 3. Traverse the AST and emit bytecode. +//! +//! The output of this analysis is a `ScopeDataMapAndFunctionMap` +//! describing each scope, binding, and function in the AST. + +mod builder; +pub mod data; +pub mod free_name_tracker; +mod pass; + +extern crate jsparagus_ast as ast; +extern crate jsparagus_stencil as stencil; + +use ast::visit::Pass; + +pub use builder::ScopeBuildError; +pub use pass::ScopePassResult; + +/// Visit all nodes in the AST, and create a scope data. +/// +/// `ast` must already have been checked for early errors. This analysis does +/// not check for errors, even scope-related errors like redeclaration of a +/// `let` variable. +pub fn generate_scope_data<'alloc, 'a>( + ast: &'alloc ast::types::Program<'alloc>, +) -> ScopePassResult { + let mut scope_pass = pass::ScopePass::new(); + scope_pass.visit_program(ast); + scope_pass.into() +} -- cgit v1.2.3