this post was submitted on 19 Aug 2023
61 points (94.2% liked)

Rust Lang

709 readers
5 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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 16 points 1 year ago (2 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?

[–] [email protected] 14 points 1 year ago* (last edited 1 year ago)

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

[–] [email protected] 3 points 1 year ago (1 children)

One of the main reasons would be to try and hide what’s in it

If, for example, you wanted to add tracking code into the generated code, and knew people would stop using your product if they found out

[–] [email protected] 2 points 1 year ago (1 children)

Is there anything confirmed yet? Like what is inside this precompiled binary?

[–] Anders429 4 points 1 year ago (1 children)

As far as I know, no one has yet been able to reproduce the binary with the source code, so I don't think the contents of it are confirmed at all.

[–] [email protected] 1 points 11 months ago

Tracking bullshit is very easy to find. Check for networking syscalls and done.