[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology

Name
Options
Comment
Verification
4chan Pass users can bypass this verification. [Learn More] [Login]
File
  • Please read the Rules and FAQ before posting.
  • You may highlight syntax and preserve whitespace by using [code] tags.

08/21/20New boards added: /vrpg/, /vmg/, /vst/ and /vm/
05/04/17New trial board added: /bant/ - International/Random
10/04/16New board for 4chan Pass users: /vip/ - Very Important Posts
[Hide] [Show All]


[Advertise on 4chan]


File: 1746904115278786.png (10 KB, 200x200)
10 KB
10 KB PNG
each day we stray farther from God's light
>>
>>108566418
I don't get the hate, it's a very useful construct to have, is it literally because "it looks icky"? Woman-tier reasoning
>>
>>108566475
Rust should've just used the fish operator for all generics, not just functions. It breaks consistency when you say Vec<i32> over here and .collect::<Vec<i32>>() over there. It should be .collect::<Vec::<i32>>() for consistency sake.
>>
>>108567047
>.collect::<Vec::<i32>>()
i'm pretty sure you could do that though
>>
>>108567071
But the problem is that it's not enforced.
>>
>>108566475
fpbp
>>
>>108567090
enforce it upon yourself
>>
>>108567047
it was only done to appease C++ users anyway. turbofishy was more for parser ambiguity reasons. I don't really fucking care either way.
it's so fucking stupid to whine about this.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.