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

Decide policy for exporting utilities and helper types. #292

Open
lthibault opened this issue Aug 21, 2022 · 1 comment · Fixed by #293
Open

Decide policy for exporting utilities and helper types. #292

lthibault opened this issue Aug 21, 2022 · 1 comment · Fixed by #293
Milestone

Comments

@lthibault
Copy link
Collaborator

As per Matrix discussion, we need to come to a decision on how to handle exported utility types such as mpsc that are orthogonal to Cap'n Proto. Three options come to mind:

  1. Consider go-capnproto2 as something approximating a monorepo => export under root-level util/* packages
  2. Split utilities into stand-alone repositories, e.g. zenhack/mpsc
  3. Create a separate util repository
@lthibault lthibault added this to the 3.0 milestone Aug 21, 2022
@lthibault lthibault mentioned this issue Aug 21, 2022
@zenhack
Copy link
Contributor

zenhack commented Aug 21, 2022

Reopening; "resolve" in a commit message triggers closing the issue.

@zenhack zenhack reopened this Aug 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants