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.

Sign up for GitHub

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

Jump to bottom

Split Name infrastructure to string slices-based and owned strings-based #38

Closed
netvl opened this issue Dec 17, 2014 · 1 comment
Closed

Split Name infrastructure to string slices-based and owned strings-based #38

netvl opened this issue Dec 17, 2014 · 1 comment
Labels
architecture necessary

Comments

@netvl
Copy link
Owner

netvl commented Dec 17, 2014

The writer should consume slice-based objects, and the reader must return owned objects.

Ideally I would like to base it on the existing Cow infrastructure which looks like a natural choice for this, but it is really tied to unsized types, and I don't see any way to use it for complex structures like Name which represents namespaced XML names with various components.
@netvl
Copy link
Owner Author

netvl commented Apr 30, 2015

Hmm, it seems I already fixed this via OwnedName/Name distinction, and I don't think it is possible to use Cow and such for this.

@netvl netvl closed this as completed Apr 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
architecture necessary
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@netvl