Skip to content

Depend on bytemuck_derive rather than bytemuck with the derive feature#1667

Open
nicoburns wants to merge 1 commit intogooglefonts:mainfrom
nicoburns:direct-bytemuck-derive
Open

Depend on bytemuck_derive rather than bytemuck with the derive feature#1667
nicoburns wants to merge 1 commit intogooglefonts:mainfrom
nicoburns:direct-bytemuck-derive

Conversation

@nicoburns
Copy link
Contributor

This is a small win for build paralellisation (meaning that the bytemuck crate doesn't need to wait for bytemuck_derive to be compiled).

Signed-off-by: Nico Burns <nico@nicoburns.com>
@nicoburns nicoburns force-pushed the direct-bytemuck-derive branch from e06f288 to b475852 Compare September 23, 2025 17:06
@rsheeter
Copy link
Collaborator

Apologies, lost track of this. Are you observing a measurable difference from this?

@cmyr
Copy link
Member

cmyr commented Nov 17, 2025

Yea I have no objection to this but I'm very curious to know the mechanism by which this improves things :)

@nicoburns
Copy link
Contributor Author

Apologies, lost track of this. Are you observing a measurable difference from this?

It's measurable, but it's pretty small (< 1s)

Yea I have no objection to this but I'm very curious to know the mechanism by which this improves things :)

The improvement comes from improving parallelism/pipelining in the build.

@cmyr
Copy link
Member

cmyr commented Nov 17, 2025

The improvement comes from improving parallelism/pipelining in the build.

Can you elaborate? Does this somehow let us start building one of the crates earlier? If yes.... why? (to be clear, I'm really just curious to understand the mechanism here :))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants