setapi: avoid duplicate setFileAPI() calls for clear log output

Before this change, the cleanup() function would unconditionally call setFileAPI.
That is not incorrect (ultimately a no-op), but results in confusing log output.

PiperOrigin-RevId: 707512218
Change-Id: Id1db4f53a7043f6c6b10500345faf809791bd714
Reviewed-on: https://go-review.googlesource.com/c/open2opaque/+/637356
Reviewed-by: Chressie Himpel <chressie@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Michael Stapelberg <stapelberg@google.com>
Auto-Submit: Michael Stapelberg <stapelberg@google.com>
1 file changed
tree: a6b96bd4857e61f9c66bbdac6d336bc2f88b991e
  1. internal/
  2. testdata/
  3. CONTRIBUTING.md
  4. gen.go
  5. genprotos.go
  6. gentestdata.go
  7. go.mod
  8. go.sum
  9. LICENSE
  10. open2opaque.go
  11. open2opaque_flush.go
  12. README.md
  13. regenerate.bash
README.md

open2opaque

The program open2opaque migrates Go code using Go Protobuf from the Open API to the Opaque API.

See https://go.dev/blog/protobuf-opaque for context.