Hi, Until this day I used to think that one can always substitute one for another. The annotation is good: use chrono::{DateTime, Utc}; ... let stamp: DateTime<Utc> = p.metadata().unwrap().created().unwrap().into(); an attempt at turbofishing let stamp = p.metadata().unwrap().create…

Because Into::into has no type argument, you cannot turbofish (is turbofishing a verb?) that method. But Into has a type argument, so you can do: fn main() { let _i: i32 = 5; let _big = Into::<i64>::into(_i); } ( Playground ) P.S.: Idiomatically, I'd rather write: i64::from(_i) (without tur…

Replace type annotation with turbofish

help

steffahn January 9, 2022, 12:42pm 3

FYI, I found that limitation annoying, so here's a workaround

3 Likes

Trait that automatically implies several From implementations?

Topic		Replies	Views
[solved] Auto conversion between types help	2	522	January 12, 2023
Mismatched types expected struct `DateTime<Utc>` found struct `DateTime<FixedOffset> help	5	2339	May 12, 2022
Turbo fish style community	7	1161	September 26, 2020
Type inference for Result<Option<T>, ()>.unwrap().unwrap() help	4	1188	January 12, 2023
Recommendations around "undesirable" extra turbofish arguments	4	303	January 25, 2023

Replace type annotation with turbofish

Related Topics