Why some providers are implemented in a separate package?

[sambartik]

Hi, I've been looking around and saw there are quite a lot providers included in the rig-core package in its rig crate. However, some providers like VertexAI are implemented in a totally different package: rig-vertexai - both of which are in this same monorepo.

What is the reasoning behind that? If shortening compile times and dependency bloat might have been the reason, why not just hide that behind an optional feature flag? Could someone bring me into the loop? Thanks!

[joshua-mo-143]

Mostly because we would rather not spawn a huge feature graph (even if optional), and once you add something and discover you made a mistake because of an unknown side-effect then it's much harder to remove it.

There might be scope for this in the future, but it's not something we're prioritising at the moment. This is also a common feature in other Rust crate families (serde, axum although axum-extra is primarily feature-gated as a means for features, etc...) so it's not unique to Rig.