pub struct RsGenerator { /* private fields */ }Expand description
Rust code generator implementing the CodeGenerator trait.
Implementations§
Source§impl RsGenerator
impl RsGenerator
Trait Implementations§
Source§impl CodeGenerator for RsGenerator
impl CodeGenerator for RsGenerator
Source§fn generate_project(
&self,
modules: &[(&AIRModule, &Path)],
) -> Result<GeneratedCode, CodegenError>
fn generate_project( &self, modules: &[(&AIRModule, &Path)], ) -> Result<GeneratedCode, CodegenError>
Emit a per-module native Rust module tree (spec §20.6.1; DQ19
resolved): each module the entry program reaches through a real use is
emitted to its own .rs file under src/, wired with Rust’s native
module system (mod <m>; declarations + use crate::<m>::<x>; for
cross-module references). This is the sole bock build output path.
§Layout (cargo-idiomatic src/-rooted crate)
Codegen emits the src/-rooted source tree (in all modes); in project
mode the scaffolder adds the Cargo.toml run affordance (S6a / DV18), so
build/rust/ becomes a runnable Cargo crate:
Cargo.toml— minimal manifest ([package]+ a[[bin]]atsrc/main.rs), emitted by the scaffolder in project mode only — just enough tocargo run.src/main.rs— the entry module’s body, preceded bymod <seg>;declarations for every top-level namespace the tree contains.src/<path>.rs— one file per reached non-entry module, mirrored from its declared module-path (module core.option⇒src/core/option.rs).src/<namespace>.rs— a wiring file per intermediate namespace (src/core.rsdeclaringpub mod option; pub mod iter; …), since Rust requires every file be reached through amoddeclaration.
§20.6.1 allows “the target ecosystem’s conventions,” so the src/-rooted
mirror is the correct idiomatic layout. The crate is run via cargo run
from build/rust/ (debug build — see the rust run plan in
bock-build’s toolchain.rs).
§Cross-module references
Each emitted file lists its cross-module dependencies as
use crate::<declared::path>::<symbol>; at the top — both the explicit
used symbols and the implicit §18.2-prelude names a module references
but does not use (e.g. a base trait in an impl). The symbols are then
referenced unqualified in the body exactly as the bundling path emitted
them, so the per-item lowering is unchanged.
The concurrency runtime (used by Channel/spawn programs) is emitted
once into a shared src/bock_runtime.rs; modules referencing it
use crate::bock_runtime::*;. Rust uses a native fn main, so no entry
invocation is appended.
Source§fn generate_tests(
&self,
modules: &[(&AIRModule, &Path)],
_framework: &str,
) -> Result<TestArtifacts, CodegenError>
fn generate_tests( &self, modules: &[(&AIRModule, &Path)], _framework: &str, ) -> Result<TestArtifacts, CodegenError>
Transpile @test functions into an inline #[cfg(test)] mod (S7).
cargo test runs the bin crate’s inline test module. Each Bock @test
becomes a #[test] fn, with expect(actual).<assertion>(expected) chains
lowered to assert! / assert_eq!. The module is emitted to
src/bock_tests.rs and wired into src/main.rs via the returned
entry_append (#[cfg(test)] mod bock_tests;). framework is ignored:
cargo test is the universal Rust framework (§20.6.2).
Source§fn target(&self) -> &TargetProfile
fn target(&self) -> &TargetProfile
Source§fn generate_module(
&self,
module: &AIRModule,
) -> Result<GeneratedCode, CodegenError>
fn generate_module( &self, module: &AIRModule, ) -> Result<GeneratedCode, CodegenError>
Source§fn needs_ai_synthesis(&self, node: &AIRNode) -> bool
fn needs_ai_synthesis(&self, node: &AIRNode) -> bool
true when the given AIR node should go through Tier 1
AI synthesis (§17.2, Q3 amended). Read moreSource§fn entry_invocation(&self, main_is_async: bool) -> Option<String>
fn entry_invocation(&self, main_is_async: bool) -> Option<String>
main function
as the entry point for this target, or None if the target has a
native entry-point convention (Rust fn main, Go func main) that
runs without a synthetic call. Read moreSource§impl Debug for RsGenerator
impl Debug for RsGenerator
Auto Trait Implementations§
impl Freeze for RsGenerator
impl RefUnwindSafe for RsGenerator
impl Send for RsGenerator
impl Sync for RsGenerator
impl Unpin for RsGenerator
impl UnsafeUnpin for RsGenerator
impl UnwindSafe for RsGenerator
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self with the foreground set to
value.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red() and
green(), which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg():
use yansi::{Paint, Color};
painted.fg(Color::White);Set foreground color to white using white().
use yansi::Paint;
painted.white();Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self with the background set to
value.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red() and
on_green(), which have the same functionality but
are pithier.
§Example
Set background color to red using fg():
use yansi::{Paint, Color};
painted.bg(Color::Red);Set background color to red using on_red().
use yansi::Paint;
painted.on_red();Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute value.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold() and
underline(), which have the same functionality
but are pithier.
§Example
Make text bold using attr():
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);Make text bold using using bold().
use yansi::Paint;
painted.bold();Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi Quirk value.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask() and
wrap(), which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk():
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);Enable wrapping using wrap().
use yansi::Paint;
painted.wrap();Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting() due to conflicts with Vec::clear().
The clear() method will be removed in a future release.
fn clear(&self) -> Painted<&T>
renamed to resetting() due to conflicts with Vec::clear().
The clear() method will be removed in a future release.
Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted only when both stdout and stderr are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);