or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Syncing
xxxxxxxxxx
Reading notes: How (and why) nextest uses tokio, part 1
Link to document: https://sunshowers.io/posts/nextest-and-tokio-1/
tags:
reading-club
Leave questions, observations, discussion topics below.
Topic
name: prompt
Questions
Observations
(vincenzopalazzo) I disagree, message passing in thread is painful in my experience.
(vincenzopalazzo) Async IO make some scalable some test suite case, such as some test that deal with IO (save file, or monitor event with a log file)
(eholk) To me one of the key observations was that the async ecosystem gives you composable building blocks for dealing with asynchrony. Before the author had to use several bespoke event systems, like channels, signals, file descriptors, etc. After moving to async, these were all unified under a more generic async/await framework.
(eholk) It's interesting that the author makes such a big deal about
select!
. I wonder if other combinators would work just as well? Was cancellation an issue for the author?(tmandry, in absentia) I didn't see an issue with cancellation but they do say:
So I feel like this is a sign that select was still a source of bugs. I wonder if you could write this code using some of the primitives Yosh was exploring, like merged streams.
(eholk) Good point! I think it'd be interesting to try merged streams and such here.
(vincenzopalazzo) This should never happens while use a runtime, right? maybe while you are developing a runtime yes, because it is a bug otherwise what it is a use cause that can cause this panic?
(tmandry) Select polls futures after completion, you have to
.fuse()
them if they don't support it.(eholk) Ah, that makes sense that it comes from
select!
, I was thinking if you're using.await
it should be pretty much impossible to poll a future after completion.