Oli Scherer

The issues raised in https://github.com/serde-rs/serde/pull/2021 are not really resolved by this. I think this is a feature needed commonly enough that we could probably quickly figure out a small robust...

Going to close this as I don't see it landing in this form any time soon.

For now you can create a git repo with this repo as a submodule and create your crate that way. It'll be on you to update then, but that was...

I don't know what would be needed on the rustc side to support invoking proc macros from other proc macros, but it doesn't seem insurmountable if the lang team agrees...

> Yup but that's a burden for libraries developers not for `serde` maintainers right ? Oh yea I meant problems for you if you go with the submodule approach and...

I mean a literal `git submodule`, not a git dependency. Git submodules are not something cargo understands or cares about, it treats them as just normal files

You don't need that. You can point a module to any file, so your crate can have a module that is defined wherever the current files are

> else I'd have to make 7 `#[path = ".../XX"] mod XX;` one for each module at the root of `serde_derive`) That seems not too bad to me. If your...

They just test compilation, not execution actually producing `Cow::Borrowed`

@dtolnay this seems like a good addition to serde. even if it could live out of tree, it's for basic libstd types