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

Move UninitializedFieldError to derive_builder #206

Merged
merged 2 commits into from Apr 21, 2021
Merged

Move UninitializedFieldError to derive_builder #206

merged 2 commits into from Apr 21, 2021

Conversation

TedDriggs
Copy link
Collaborator

UninitializedFieldError is part of the runtime API of derive_builder,
not part of its compile-time macro machinery. Exporting it from the
derive_builder_core crate caused downstream crates to unnecessarily
import all of derive_builder_core, rather than only importing it via
the proc-macro crate at compile-time.

Fixes #201

UninitializedFieldError is part of the runtime API of derive_builder,
not part of its compile-time macro machinery. Exporting it from the
derive_builder_core crate caused downstream crates to unnecessarily
import all of derive_builder_core, rather than only importing it via
the proc-macro crate at compile-time.

Fixes #201
@TedDriggs
Copy link
Collaborator Author

@andy128k any idea why this fails when the original PR adding the test succeeds? I'm very unfamiliar with no_std.

This is causing a CI failure which blocks fixing no_std support
@TedDriggs
Copy link
Collaborator Author

Filed an issue to bring back the removed test, so proceeding to merge.

@TedDriggs TedDriggs merged commit b018068 into master Apr 21, 2021
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 this pull request may close these issues.

Can't compile v0.10.0 in the no_std environment
1 participant