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

Don't depend on alloc when disabling the read_core and write_core features #328

Closed
bjorn3 opened this issue Jun 29, 2021 · 0 comments · Fixed by #336
Closed

Don't depend on alloc when disabling the read_core and write_core features #328

bjorn3 opened this issue Jun 29, 2021 · 0 comments · Fixed by #336

Comments

@bjorn3
Copy link
Contributor

bjorn3 commented Jun 29, 2021

liballoc is only used by the higher level reading and writing code. When using object just for the raw object file structures and constants, it causes #[global_allocator] to be necessary despite not being used.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Move Bytes to read::util philipc/object
1 participant
@bjorn3