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

Things fail with weird errors if your atlas doesnt know about all your types #14

Open
whyrusleeping opened this issue Nov 22, 2017 · 0 comments

Comments

@whyrusleeping
Copy link
Collaborator

I had a type that looked something like:

type A struct {
  Foo []B
}

type B struct {
  Cats uint64
  ParrotQuote string
  DungHeap Heap
}

type Heap struct {
  // heap related fields
}

And I only made an atlas entry for A. When marshaling an instance of A however, it failed with cryptic messages such as "value already consumed". I finally figured out that making atlas entries for B and Heap made things happier, but it took me a while.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants