You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is ideal to try and group common code between lighthouse and anchor.
However, we don't want to pull the entire world of lighthouse for tiny pieces of shared code. Often the solution is modularize lighthouse into small crates or feature-gate components that we need.
In the initial building of Anchor this process has been slow and we have been simply importing lighthouse crates, but at a significant compile time cost.
Using cargo tree can help see some of the larger crates.
Anything that pulls the eth2 crate is too large.
I will try and list crates that we can try and reduce here as we go, but this issue is to try and significantly reduce the dependency tree where we can.
warp_utils in our http_metrics crate is a good example.
The text was updated successfully, but these errors were encountered:
It is ideal to try and group common code between lighthouse and anchor.
However, we don't want to pull the entire world of lighthouse for tiny pieces of shared code. Often the solution is modularize lighthouse into small crates or feature-gate components that we need.
In the initial building of Anchor this process has been slow and we have been simply importing lighthouse crates, but at a significant compile time cost.
Using
cargo tree
can help see some of the larger crates.Anything that pulls the
eth2
crate is too large.I will try and list crates that we can try and reduce here as we go, but this issue is to try and significantly reduce the dependency tree where we can.
warp_utils
in ourhttp_metrics
crate is a good example.The text was updated successfully, but these errors were encountered: