this post was submitted on 19 Aug 2023
49 points (100.0% liked)

Rust Lang

117 readers
1 users here now

Rules [Developing]

Observe our code of conduct

Constructive criticism only

No endless relitigation

No low-effort content

No memes or image macros

No NSFW Content

founded 1 year ago
MODERATORS
 

serde_derive now ships a precompiled binary. This made a lot of people angry. The crate maintainer finally locked the issue.

top 7 comments
sorted by: hot top controversial new old
[–] rust@midwest.social 21 points 1 year ago

To me, the fact that the issue was just outright dismissed by the maintainer without really answering any of the legitimate concerns raised (disregarding the unnecessary personal attacks in a few comments) is pretty concerning. And now the issue has been locked without a really good response.

[–] Sibbo@sopuli.xyz 14 points 1 year ago (4 children)

Can someone explain why one would want to precompile procedural macros? Don't they get compiled only once anyways, when compiling a dependent crate for the first time? So compile time should be not that relevant?

[–] anlumo@feddit.de 13 points 1 year ago* (last edited 1 year ago)

You’re correct, and that is part of the controversy.

[–] isosphere 3 points 1 year ago (1 children)

I've read the thread; Rust-folk I recognize seem to accept that this was done to reduce compile time without suspecting bad-faith, but I can't independently verify that.

There's a post in there where sometime tries to manually compile the same binary to verify that it matches the shipped binary and they were not able to do it, but there could be a good reason for that. Reproducible builds are hard.

load more comments (1 replies)
load more comments (2 replies)
[–] bet@lemm.ee 4 points 1 year ago

Thanks, I hadn't seen this elsewhere, glad to know about it.

[–] Mubelotix@jlai.lu 3 points 1 year ago

We are trusting too many people