Skip to content

Conversation

@zzau13
Copy link
Contributor

@zzau13 zzau13 commented May 1, 2020

Closes #216

Copy link
Owner

@dtolnay dtolnay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer not to accept this because it breaks error reporting of unrelated macros in any codebase that pulls in your library.

Instead we can consider factoring the fallback implementation in a way that can be published under a separate crate name, kind of like how https://crates.io/crates/serde_derive_internals is published from inside the serde_derive internals.

@zzau13
Copy link
Contributor Author

zzau13 commented May 1, 2020

I use it within syn.

So, should we implement some solution to force use the fallback in syn?

@dtolnay
Copy link
Owner

dtolnay commented May 1, 2020

Could you confirm that #220 resolves your use case?

@zzau13
Copy link
Contributor Author

zzau13 commented May 1, 2020

Yes, it would be solved.

Thanks!!

@zzau13 zzau13 closed this May 1, 2020
Repository owner locked and limited conversation to collaborators May 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add feature for force not(wrap_proc_macro)

2 participants