yayagram VS logos

Two crates: - parse-size is criminally underrated. It allows you to parse input like "100 MB", "50 kb", "25b" into an integer of bytes. It parses input so intuitively and it works exactly the way I expected. I use it in https://github.com/r00ster91/splitter. - line_drawing is in my opinion the best line algorithm library there is. Extremely clean and nice to use. Exactly what I need for my project https://github.com/r00ster91/yayagram.

Still working on this puzzle game playable in the terminal with the mouse: https://github.com/r00ster91/yayagram In version 0.5.0 I've added a feature to darken all cells in a specific direction from the pointer but now I've figured out that a much better way is to constantly darken all cells in the four directions of the mouse pointer.

This is the repository with much more information in the README.md: https://github.com/r00ster91/yayagram, including an example at the bottom that might help you understand the game better if you are new to this kind of puzzle game. See also: https://en.wikipedia.org/wiki/Nonogram.

Hello Rustaceans. This is a clone of the puzzle game picross (also known as nonograms, griddlers and some other names) but with some additions and novelty, like a blue grid cell (wasn't used in this video) and an editor. If you want to try it, you can install the game with cargo install yayagram. Here is the repository with much more information in the README.md: https://github.com/r00ster91/yayagram, including an example that might help you understand the game better if you are new to this puzzle game.

Today I released the puzzle game yayagram which is picross/nonograms but for the terminal. I've been working on it for what feels like months now and it has really come a long way.

This is mighty impressive! I've been trying to get some motivation for the mythical rewrite of the proc macro in Logos, and this might just do it for me :D. I'll have a proper look later today and see if any of your findings have something that can be generalized. Also really surprised to see aarch64 doing better than x86_64 since the latter is what I've been optimizing for!

Rust is a very nice langage for implementing compilers, and has a nice ecosystem for it (logos, rust-peg, lalrpop, astmaker -- this one is mine --, etc...).

rust-langdev has a lot of libraries for building compilers in Rust. Perhaps you could use these to make your implementation easier, and revisit it later if you want to build things from scratch. I'd suggest logos for lexing, LALRPOP / chumsky for parsing, and rust-gc for garbage collection.

Thanks! For compile times you might find the CLI version that Andrew Hickman contributed useful, it's undocumented still mostly I fear but shouldn't be hard to use, see original PR: https://github.com/maciejhirsz/logos/pull/248

For my lexer generation purposes, I tend to use https://github.com/maciejhirsz/logos, as it not only generates an easy to use lazy lexer, but the result is also exceptionally fast!

Hi, I'm using rowan to create a parser and want to print more useful error messages with position in the text/file. I'm using logos (https://crates.io/crates/logos) to generate the lexer. Is there a way to get the starting and ending positions of a SyntaxToken? If not I thought of adding my own wrapper struct around the SyntaxTokens.

Is there a way for a lexer created with the logos crate (https://crates.io/crates/logos) to get the starting and ending positions for the tokens?

I wouldn't recommend Logos at this point. This recent bug is quite nasty and seems easy to hit, and the maintainer is unresponsive. Last commit was half a year ago. At this point I consider Logos abandonware, though it would be great if its development continued, or if it were forked.

logos uses "ridiculously fast".