Victor LEFEBVRE

> I think this is a feature needed commonly enough that we could probably quickly figure out a small robust rust language feature to allow you to call proc macros...

> For now you can create a git repo with this repo as a submodule and create your crate that way. Haha, I honestly didn't even thought about submodules, thanks...

Oh, I thought you were saying that for serde and the PR itself, yup it could become a pain for me and others if serde changes too much. I didn't...

Hi, sorry to bother you again 🙇 about > For now you can create a git repo with this repo as a submodule and create your crate that way. how...

Yeah thats what I tried but the files weren't getting used during publish, I finally found a way to get it to work properly (see [here](https://github.com/vic1707/serde-versioning/tree/serde-derive-impl-as-a-submodule) if interested) 🥳 ---...

It's what I tried but since `serde_derive` and the whole `serde` repo contains a lots of symlinks (vscode was fine with that but cargo always failed to build), and imports...

After re-re-re-...-re reading your comment I think I finally understood what you were talking about ```rs #[path = "../serde/serde_derive_implementation/src/mod.rs"] mod serde_derive_implementation; ``` and using it like ```rs use crate::serde_derive_implementation::de::expand_derive_deserialize; ```...

But using ```rs #[path = "../serde/serde_derive/src/implementation/mod.rs"] mod implementation; #[path = "../serde/serde_derive/src/internals/mod.rs"] mod internals; ``` I can get `cargo build` to work but not `cargo publish` despite adding `"serde/**/*"` to the...

Ok then, will work with that for now then 👍

Oh ok, easy fix indeed. Thought for another user + public repo meant I could omit the token 👍 As for my question about organization (I believed it got lost...