Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

schema: use separate package for capnpc-go and reflection usages #83

Closed
zombiezen opened this issue May 16, 2017 · 0 comments
Closed

schema: use separate package for capnpc-go and reflection usages #83

zombiezen opened this issue May 16, 2017 · 0 comments
Assignees
Labels
Milestone

Comments

@zombiezen
Copy link
Contributor

To avoid cyclic dependency problems and to make std/capnp/schema not special (i.e. include String() methods etc.), all of the packages in this repository that currently use std/capnp/schema should be made to use a new internal-only package that has the current generated code. This would not be a breaking change, as none of the public API surface exposes any of these types. The packages just use the schema package to implement the internals.

@zombiezen zombiezen self-assigned this May 16, 2017
@zombiezen zombiezen modified the milestone: 2.15 Jun 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant