-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Feature #rust more prominently in docs #3432
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'd been thinking about this and wondering if you'd be willing to go a step further, by hosting a web-based IRC client linked directly from the front page. Freenode does this using qwebirc (also used by QuakeNet, and EFNet, and the W3C, and, well, basically everyone except moznet). See http://webchat.freenode.net/ for an example. |
That would be great. I wonder Mibbit can be used for that. There's also an open source mibbit competitor called wsirc. |
I've put Mibbit links on rust-lang.org, in the tutorial, and in multiple prominent places on the wiki. |
run GC stress test only for host tests I suspect these are a significant contributor to our Linux CI job being by far the slowest currently. Let's see. We have Linux, Windows, and macOS hosts so all major OSes are still covered.
Starting from rust-lang.org I couldn't find any documentation about #rust, which is by far the most useful place to go for information about Rust. There are links to the IRC logs, but it doesn't really explain the supreme importance of #rust.
It would be great if rust-lang.org could make that clear somehow.
The tutorial could end (or begin) with links to further information, including emphasizing #rust.
The text was updated successfully, but these errors were encountered: