Project Interop
Targo works best when it cooperates with Go projects instead of pretending Go does not exist.
Common patterns
- add Targo source into an existing Go module
- import Go standard library and third-party packages directly
- treat emitted Go as a build artifact, not the authoring source
Workflow advice
- confirm
go.mod - confirm
targo.json - refresh declarations after import or dependency changes
- keep generated output out of manual edits