You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is probably because the commands in Channels, IO, and Framing do not create any output, and without $, multiple commands are easier to copy and paste (more ergonomic).
In contrast, in Hello tokio there is a command with output:
$ cargo run
got value from the server; result=Some(b"world")
Solutions
Thus, there are multiple solutions:
Use $ consistently
Less ergonomic for multiple commands in one block; see the first block in Hello Tokio.
Drop $ consistently
More ergonomic, but commands are less evident due to missing $ Means rewriting the command in Hello Tokio shown above to distinguish commands from output. This is already done at the end of the Setup section.
We could highlight bash scripts differently (currently, I do not see a difference between text and bash) to distinguish them from other code blocks representing the output (not exactly sure how to do this yet).
Leave it as is.
Let me know what you think!
I can draft a pull request for 1 or 2 if you like.
The text was updated successfully, but these errors were encountered:
The bash scripts are displayed inconsistently across the tutorial, which is a bit confusing and sometimes less ergonomic when following the tutorial.
Problem
For example, in Hello tokio and Spawning the following is used (mind the $, and language=bash):
In Streams, $ is used but not language=bash, which is fine but could be changed.
However, later in Channels, IO, and Framing scripts are shown as follows (mind the missing $, and language=text not bash):
This is probably because the commands in Channels, IO, and Framing do not create any output, and without $, multiple commands are easier to copy and paste (more ergonomic).
In contrast, in Hello tokio there is a command with output:
Solutions
Thus, there are multiple solutions:
Let me know what you think!
I can draft a pull request for 1 or 2 if you like.
The text was updated successfully, but these errors were encountered: