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
Currently (as @dzmitry-huba pointed out), it is too easy to mix and match dependencies so that a crate ends up with multiple versions of prost that are incompatible with each other.
We should consider re-exporting prost (and maybe even prost-derive) from our own crates (not sure which ones? maybe micro_rpc, maybe others), and use the re-exported versions instead of adding a direct dependency on prost from the application crate.
The text was updated successfully, but these errors were encountered:
Currently (as @dzmitry-huba pointed out), it is too easy to mix and match dependencies so that a crate ends up with multiple versions of prost that are incompatible with each other.
We should consider re-exporting prost (and maybe even prost-derive) from our own crates (not sure which ones? maybe micro_rpc, maybe others), and use the re-exported versions instead of adding a direct dependency on prost from the application crate.
The text was updated successfully, but these errors were encountered: