So @Yoshua Wuyts I am having a few unanticipated concerns arise as I try to move my "guessing game" edits into proper testable snippets. Here are a few of them:
stream.split()-- actually, this seems probably ok, as we can basically explain what it does and give a "forward ref" to the streams chapter where you will explain it
failure::Error, but I was hoping to avoid referencing
failure. Annoyingly, you can't actually use
Box<dyn Error + Send>because (dear god) there is no
Fromimpls for doing the conversion from
std::io::Error(those exist only for
Box<dyn Error>, :cry: )
hoping to avoid referencing failure
Shameless self-promotion, but SNAFU has built-in futures 0.1 and 0.3 support :-)
I’m sure that you just want to avoid using any crates, though.
I've not really looked at SNAFU, I must admit
@nikomatsakis you can use
Box<dyn Error + Send + Sync>
I’d appreciate an aside about “we are doing convenient error handling to focus on async and not advocating any particular style” (so long as that’s true). People tend to copy-paste and then treat as gospel such examples.
I think the sad truth is I wouldn't know what error handling style to recommend
Do you think we'd be considering a 1.0 [runtime release] at any point?
@nikomatsakis Yeah definitely, though I think the first milestone is to get us off alpha.x releases. Which kind of depends on futures-rs moving off there too.