Recently withoutboats posted a series of blog posts about some syntax sugar he would like added to Rust.
The gist of it is, as far as I can tell, there should be some way to not have to
write Ok(...)
for the happy path in functions which return Result
. He
specifically is advocating for a throws
keyword that would go a bit beyond
just this basic change, but the problem he’s mainly trying to fix is having to
type Ok(...)
so often.
I haven’t really been involved with the Rust community that much, especially
since I stopped working on Way Cooler. This isn’t from lack of using Rust, I
use Rust in my day job after all, but rather from disinterest in getting
involved in what seems to be mostly bikeshedding. The .await
war was the final
straw to make me stop watching the Rust community beyond what comes in the
release notes.
So in many ways I’m coming into this argument as an outsider – I have not read
any thing beyond the two linked blog posts and am missing most of the discussion
that has gone on. I’m not going to weigh in on throws
vs some annotation vs
Fehler because even though I have an opinion I detest bikeshedding.
However, as a long time user of Rust (4 years, wow how time flies!) the
constantly changing standard of what constitutes “idiomatic Rust” is starting to
wear me down. try!()
-> ?
, the addition of impl trait
, and the dyn
keyword are all features that have changed what it means to write idiomatic
Rust. When these features come out I need to now change my code in order to keep
it idiomatic.
That’s not to say I hate these features. I remember being very happy when ?
came about and dyn
is certainly clearer than what we had before. However
having to make these superficial changes again and again causes churn in all my
codebases. Because Rust releases every 6 weeks that means every 6 weeks I might
need to make superficial changes to my codebase (not to mention potentially have
to do a major point release – using impl
is an API breaking change).
So to bring my complaints back around to the issue at hand: if Ok
wrapping
came in the next Rust release this would be another change that requires me to
update my code in order to be idiomatic. This isn’t sustainable for me – I
appreciate Rust team’s commitment to backwards compatibility but the constant
disregard for forwards-compatibility makes me feel like I’m on a treadmill
trying, and failing, to keep up.
以上就是本文的全部内容,希望对大家的学习有所帮助,也希望大家多多支持 码农网
猜你喜欢:本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们。
复盘+:把经验转化为能力(第2版)
邱昭良 / 机械工业出版社 / 39.00
随着环境日趋多变、不确定、复杂、模糊,无论是个人还是组织,都需要更快更有效地进行创新应变、提升能力。复盘作为一种从经验中学习的结构化方法,满足了快速学习的需求,也是有效进行知识萃取与共享的机制。在第1版基础上,《复盘+:把经验转化为能力》(第2版)做了六方面修订: ·提炼复盘的关键词,让大家更精准地理解复盘的精髓; ·基于实际操作经验,梳理、明确了复盘的"底层逻辑"; ·明确了复......一起来看看 《复盘+:把经验转化为能力(第2版)》 这本书的介绍吧!
URL 编码/解码
URL 编码/解码
UNIX 时间戳转换
UNIX 时间戳转换