QWASR Rust Codegen FAQs

Question 1

What is the primary input required for the codegen skill?

Accepted Answer

It primarily requires an Intermediate Representation (IR) file, typically generated by an analyzer skill, which contains the analyzed behavior specification of the source logic.

Question 2

Does this skill generate unit tests for the Rust code?

Accepted Answer

No, this skill explicitly omits test generation. Testing is handled by separate host applications or specialized testgen skills to maintain a strict separation of concerns.

Question 3

Why does it restrict standard Rust crates like tokio or reqwest?

Accepted Answer

To ensure WebAssembly compatibility, the skill enforces guardrails against crates that rely on forbidden APIs like direct file access or threading, replacing them with QWASR provider traits.

Question 4

Can I use custom error types in the generated public API?

Accepted Answer

No, all public-facing errors must return the qwasr_sdk::Error type to ensure consistency and compatibility across the runtime boundary.

Question 5

How is external I/O handled in the generated crates?

Accepted Answer

All I/O flows through provider-based dependency injection using specific traits like Publisher for messaging, HttpRequest for network calls, and TableStore for database access.

QWASR Rust Codegen

Key Features

Use Cases

QWASR Rust Codegen

Key Features

Use Cases