Google Git
Sign in
vanadium / release.go.x.ref / 0be8541bf3c104b69a2b972d2b2c3998abbcc605
commit0be8541bf3c104b69a2b972d2b2c3998abbcc605[log] [tgz]
authorAdam Sadovsky <asadovsky@gmail.com>Mon May 02 13:16:30 2016 -0700
committerAdam Sadovsky <sadovsky@google.com>Mon May 02 21:20:33 2016 +0000
tree4a768367732cbc859b679eda2182fd4a930be4ee
parentb9a4338e7ee587e8b994cf4d974e7ef243f0971e [diff]
mojo.syncbase: syncbase: minimal updates to mojo, for sanity

I'm about to do something similar for Cgo (similar API and
implementation strategy), so I wanted to minimally update
mojo to have something reasonable to work against. The mojo
code certainly won't compile in its current state; various
method implementations need to be updated to reflect the API
changes. I don't plan to make further changes to the mojo
code at this time.

MultiPart: 1/2
Change-Id: Ic4ee76a46c3ef38839f7fe705ae9d939c7ca22ba
1 file changed
tree: 4a768367732cbc859b679eda2182fd4a930be4ee
  1. cmd/
  2. examples/
  3. internal/
  4. lib/
  5. runtime/
  6. services/
  7. test/
  8. .gitignore
  9. AUTHORS
  10. CONTRIBUTING.md
  11. CONTRIBUTORS
  12. envvar.go
  13. envvar_test.go
  14. LICENSE
  15. PATENTS
  16. README.md
  17. VERSION
README.md

Vanadium

This repository contains a reference implementation of the Vanadium APIs.

Unlike the APIs in https://github.com/vanadium/go.v23, which promises to provide backward compatibility this repository makes no such promises.