chore: Extract `assets` module out of zed crate. (#3957)

This essentially shaves off about 10% off of an incremental build after
project change and potentially more if you're changing stuff like
`welcome` that's very close to the `zed` crate in the dep graph. That's
because macro expansion takes place even in incremental builds it seems?
And zed (lib) + zed (bin) could take up to 4 seconds out of an
incremental build, which is a *lot* in a 10s build. In reality though it
shaves 1 second off of 5 seconds incremental 'welcome'/ 1s off of 10s
'project' builds.

Note that we had `assets` crate in the past (removed in #2575 /cc
@maxbrunsfeld), but this is a bit different, because `assets` is a
dependency of *just* zed and nothing else. We essentially cache macro
expansion results ourselves.

Release Notes:

- N/A

This commit is contained in:

Piotr Osiewicz

2024-01-08 22:49:14 +01:00

committed by

GitHub

parent 80f204fabb

commit ae6d09b9b2

7 changed files with 28 additions and 4 deletions

									
										Cargo.toml
									
		+1
		
												View File
												
				@@ -1,5 +1,6 @@

				[workspace]

				members = [

				    "crates/assets",

				    "crates/activity_indicator",

				    "crates/ai",

				    "crates/assistant",

chore: Extract assets module out of zed crate. (#3957)

chore: Extract `assets` module out of zed crate. (#3957)