basic-computer-games
rustfmt
basic-computer-games | rustfmt | |
---|---|---|
30 | 57 | |
10,758 | 5,761 | |
- | 0.9% | |
9.1 | 8.9 | |
12 days ago | 7 days ago | |
C# | Rust | |
The Unlicense | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
basic-computer-games
-
How to solve the "Mastermind" guessing game? (2009)
This was one of the computer games from 1976 BASIC computer games that some of us worked on ports of for the Coding Horror: Basic Computer Games repo. I recall there were a number of errors in the original and thus a few in the ports, python being one. I ended up writing about the deduction logic for solving mastermind because it seemed non-intuitive.
https://github.com/coding-horror/basic-computer-games/blob/m...
- Technically not alt-prog, but could be implemented with such: a compendium of classic computer games, re-written in multiple programming languages.
-
A repository of “BASIC Computer Games” code in modern languages
This is exactly that.
% git clone https://github.com/coding-horror/basic-computer-games.git
- Basic Computer Games
-
hola, estoy aprendiendo a programar y quiero empezar un proyecto pero no tengo ideas, ¿ideas para un juego?
Puedes utilizar este repositorio como modelo: basic-computer-games
-
Ask HN: How much do you use uppercase vs. lowercase characters in your code?
Your list omits BASIC, much of which looked like this:
https://github.com/coding-horror/basic-computer-games/blob/m...
-
Python multi-level break and continue
My example was "twice by one developer", not "twice across all indexed repos."
A spot check shows that quite a few in your link are used specifically to ensure correct handling of Rust multi-level breaks work syntax, like https://github.com/rust-lang/rust-analyzer/blob/master/crate... , https://github.com/rust-lang/rustfmt/blob/master/tests/sourc... , https://github.com/rust-lang/rust/blob/master/src/tools/rust... , https://github.com/rust-lang/rust/blob/master/src/tools/rust... and likely more.
Another is a translation of BASIC code to Rust, using break as a form of goto. https://github.com/coding-horror/basic-computer-games/blob/e...
The example at https://github.com/tokio-rs/mio/blob/master/tests/tcp.rs is a nice one
// Wait for our TCP stream to connect
- I want to learn to code in Godot
- This is literally old school, a computer lab of Apple II computers that some people's schools which are literally old had decades ago, back in the 80s and 90s!
- Archimedes Spiral: Converting old-school BASIC to Python
rustfmt
-
You can't do that because I hate you
The author provides very surface-level criticism of two Rust tools, but they don't look into why those choices were made.
With about five minutes of my time, I found out:
wrap_comments was introduced in 2019 [0]. There are bugs in the implementation (it breaks Markdown tables), so the option hasn't been marked as stable. Progress on the issue has been spotty.
--no-merge-sources is not trivial to re-implement [1]. The author has already explained why the flag no longer works -- Cargo integrated the command, but not all of the flags. This commit [2] explains why this functionality was removed in the first place.
Rust is open source, so the author of this blog post could improve the state of the software they care about by championing these issues. The --no-merge-sources error message even encourages you to open an issue, presumably so that the authors of Cargo can gauge the importance of certain flags/features.
You could even do something much simpler, like adding a comment to the related issues mentioning that you ran into these rough edges and that it made your life a little worse, or with a workaround that you found.
Alternatively, you can continue to write about how much free software sucks.
[0]: https://github.com/rust-lang/rustfmt/issues/3347
[1]: https://github.com/rust-lang/cargo/pull/10344
[2]: https://github.com/rust-lang/cargo/commit/3842d8e6f20067f716...
-
Let else will finally be formatted by rustfmt soon
The new style still supports single line let-else, and there is a configuration parameter to make it be on one line also for longer lines.
-
Is rustfmt abandoned? Will it ever format `let ... else` syntax?
It seems there is an issue about this dating all the way back from 2018 but yet it still hasn't been fixed.
-
Hey Rustaceans! Got a question? Ask here (22/2023)!
However since 4179 recent versions should merge configuration files. Not sure what the details / specifics are but if just ignoring the file entirely is not good enough you might give it its own directory and rustfmt.toml file and see if that works.
-
Rustfmt refusing to work with certain functions.
Could this be be #3863 - Gives up on chains if any line is too long? It might not be, because I can't see a specific "line" that's too long to format, but there's more detail about the exact problem in the issue.
-
Rust Tips and Tricks #PartOne
Rustfmt is a tool that formats Rust code in compliance with style guidelines. Its name precisely reflects its purpose. To install rustfmt, you can run rustup component add rustfmt. Once installed, you can execute cargo fmt to format Rust code in your workspace. If you require further information, you can visit rustfmt’s GitHub repository.
-
What are some good practices when writing rust?
code must be formatted with rustfmt.
- HTML Limpo
-
Hey Rustaceans! Got a question? Ask here (5/2023)!
Yes, some cases are not yet supported (https://github.com/rust-lang/rustfmt/issues/4914).
-
How do I stop RustFmt from turning this…
Just FYI, the let-else suggestions will only work until rustfmt settles on a format for it. So you may be surprised when this happens and it suddenly changes.