Conversation
|
|
||
| ### Y U HATE RUST SO MUCH? | ||
|
|
||
| I don't, actually. I believe that those who spend their time asking people to rewrite their projects are probably not themselves active Rust developers, as those active devs are probably busy [writing memory-safe code](https://trac.torproject.org/projects/tor/ticket/11331). |
There was a problem hiding this comment.
HTTPS links have // which prevents the () from being paired, causing errors at the lexing stage. They have been migrated to footnote style which does not wrap URLs inside brackets.
| fn test() { | ||
| use std::{fs, path::PathBuf}; | ||
|
|
||
| let path = PathBuf::from(env!("CARGO_MANIFEST_DIR")).join("test.txt"); |
There was a problem hiding this comment.
The test file was made external instead of using quote!(), because quote!() does not allow literal expressions with a #.
|
The CI is currently failing because of rust-lang/cargo#8354 failing to install |
|
This is an impressive display of over-engineering. Kudos! The only thing that seems to be missing at this point is instructions for how to build the readme within the readme. |
progval
added
approved
|
I have added the instructions to build the readme. I have also added a |
README.md
Outdated
| This readme is written in Rust to further rebut arguments that Rust has low readability. | ||
| The readme can be built into an executable by running the [just][just] command: | ||
|
|
||
| > just build |
There was a problem hiding this comment.
code blocks can be inserted in markdown by indenting with four spaces.
|
Consider adding a [unsafe] block when referecing "### Y U HATE RUST SO MUCH?" |
4 participants
This would compile README into an executable rust file that would output the same contents as the markdown content.
One can obtain the executable by running
just build. Currently the justfile only supports Linux-like systems.