Closes #2538
Supercedes #2579
Follows my recommendation: #2579 (comment)
Current choice: Opt-Out (current commit)
Override via cfg(serde_derive_build = "source") to build from source
Alterative: Op...
The precompiled implementation is the only supported way to use the macros that are published in serde_derive. If there is implementation work needed in some build tools to accommodate it, someone should feel free to do that work
That seems a bit concerning. At first I was under the impression the binary was compiled on the user’s machine, but once I saw that it’s distributed with serde I can see why people are upset.
The precompiled implementation is the only supported way to use the macros that are published in serde_derive
That statement is straight up gaslighting.
The precompiled binary is only provided for one platform, Linux. Windows does not use a precompiled binary but compiles its own from the source. How can he claim it’s the “only supported way”, when for most platforms he is doing it another way? Also, the crate, throughout most of its life, has been doing it another way.
Has dtolnay shown a strong sentiment towards having it be on always? I can’t imagine there’s much reason not to make it configurable.
That sounds like he doesn’t like to (re-)introduce any other options.
That seems a bit concerning. At first I was under the impression the binary was compiled on the user’s machine, but once I saw that it’s distributed with serde I can see why people are upset.
That’s how procedural macros used to and were intended to work.
That statement is straight up gaslighting.
The precompiled binary is only provided for one platform, Linux. Windows does not use a precompiled binary but compiles its own from the source. How can he claim it’s the “only supported way”, when for most platforms he is doing it another way? Also, the crate, throughout most of its life, has been doing it another way.