31
Looks like the sede situation is being worked on
(github.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Aug 2023
31 points (94.3% liked)
Rust
5777 readers
9 users here now
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Wormhole
Credits
- The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)
founded 1 year ago
MODERATORS
My personal gut feeling: the maintainer will just shoot this attempt down and close the PR.
Happy to be proven wrong here though.
dtolnay isn't the only maintainer though. oli-obk is also a maintainer and is participating in the discussions on the PR.
I don't think oli-obk has any say in this as they stated the following:
Source
You're right, I missed that. That's unfortunate.
Technically true, but he has two merge commits in last three years. Not sure that will still give him much of a pull.
Author of the PR made it opt-out. I think it may be enough of the compromise for the maintainer.
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 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.
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.