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

Deriving TypeGenerator requires that it is in scope #105

Closed
Ekleog opened this issue Jan 3, 2023 · 0 comments · Fixed by #109
Closed

Deriving TypeGenerator requires that it is in scope #105

Ekleog opened this issue Jan 3, 2023 · 0 comments · Fixed by #109
Labels
T-Good First Issue Good for newcomers

Comments

@Ekleog
Copy link
Contributor

Ekleog commented Jan 3, 2023

I usually do not use the derive-macros that I use, so that I always know which crate they're coming from.

However, if I #[derive(bolero_generator::TypeGenerator)], rustc complains that it's referring to a not-in-scope TypeGenerator.

Ideally, TypeGenerator would refer to a full-path variant of itself, to make possible such derives.

That said it's certainly not a big deal, as the fix is simple and quite obvious, I'm just submitting this here as a probably-good-first-issue area of improvement :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Good First Issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants