Untapped potential in Rust's type system

• typetag

  9 547 5.8 Rust

  Discontinued Serde serializable and deserializable trait objects

This allows me define methods on both borrowed (`Message<&str>`) and owned (`Message`) versions without issues. When remaining inside the process, the borrowed version is passed around and when sent across the process boundaries I can deserialize it to an owned version. This problem prevent me from using Typetag and I am still not sure how it should be solved.

[0]: https://github.com/dtolnay/typetag

• assert-type-eq-rs

  1 0 0.0 Rust

  Macro to assert types across potentially different crate versions are compatible

  

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• rfcs

  666 5,713 9.8 Markdown

  RFCs for changes to Rust

  

I think this is a valid question. C++ provides std::is_same, why do Rust users need an external dependency (especially given the fact that the type system is one of Rusts major strengths)?

My best guess, going by a comment in the source code, is that this macro will not be necessary in the future (and therefore makes less sense to put in the standard library):

> Until RFC 1977 (public dependencies) is accepted, the situation where multiple different versions of the same crate are present is possible.

https://github.com/rust-lang/rfcs/pull/1977

Suggest a related project