Question 1

How do I mock an unexported function with xgo?

Accepted Answer

Use the Mock API, which supports intercepting unexported functions by name or reference, as it can handle functions with unexported types where Patch might not work, per the Mock section details.

Question 2

xgo vs bouk/monkey: which is more reliable for mocking?

Accepted Answer

xgo uses IR rewriting for better compatibility across all Go-supported OS and architectures, while monkey relies on assembly hacks limited to specific platforms, making xgo more stable and future-proof.

Question 3

Does xgo work with Go modules?

Accepted Answer

Yes, xgo fully integrates with Go modules; install it via go install and manage dependencies with go get, as shown in the quick start with go mod init and go get commands.

Question 4

How to set up xgo in Visual Studio Code?

Accepted Answer

Run xgo setup to generate an instrumented GOROOT, then add the path to .vscode/settings.json under go.goroot, following the IDE setup instructions for seamless integration.

Question 5

What's the performance impact of using xgo traces?

Accepted Answer

Trace collection adds runtime overhead, but it's configurable via --strace-dir and trace.Trace() to limit scope, balancing debug needs with performance in test environments.

Question 6

Can xgo mock closures or generic functions?

Accepted Answer

Yes, xgo supports mocking closures and generic functions with per-type isolation, using Patch or Mock APIs as outlined in the cheatsheet for per-TParam generic functions.

xgo

What is xgo?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions