# Looking for code review on my 4 small crates **URL:** \ **Category:** code review\ **Created:** [July 1, 2026, 5:27pm UTC](https://users.rust-lang.org/t/looking-for-code-review-on-my-4-small-crates/141053 "2026-07-01T17:27:41Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![egare0](https://sea1.discourse-cdn.com/flex019/user_avatar/users.rust-lang.org/egare0/32/53133_2.png) [@egare0](https://users.rust-lang.org/u/egare0)\ **Post date:** [July 1, 2026, 5:27pm UTC](https://users.rust-lang.org/t/looking-for-code-review-on-my-4-small-crates/141053/1 "2026-07-01T17:27:41Z")
Hey folks! I've been writing some Rust lately and published a few small crates over the last couple of weeks. They aren't anything super advanced, but I'd really love to get some eyes on my code to see if I'm doing things the "Rusty" way. Here are the repos: - **[claris](https://github.com/egare0/claris)** - A clean, minimal, and fluent logging framework. - **[zerec](https://github.com/egare0/zerec)** - A minimal zero-copy binary codec. - **[syntia](https://github.com/egare0/syntia)** - A lightweight toolkit for building lexers and parsers. - **[rendra](https://github.com/egare0/rendra)** - A high-level, ergonomic rendering abstraction over wgpu. (Not yet completed) Any quick feedback, nitpicks, or code review would be awesome. Cheers! ---
**Author:** ![marlez](https://sea1.discourse-cdn.com/flex019/user_avatar/users.rust-lang.org/marlez/32/52182_2.png) [@marlez](https://users.rust-lang.org/u/marlez)\ **Post date:** [July 1, 2026, 7:25pm UTC](https://users.rust-lang.org/t/looking-for-code-review-on-my-4-small-crates/141053/2 "2026-07-01T19:25:48Z")
LGTM. No obvious anti-patterns/unidiomatic use cases, as far as I can tell. Out of sheer curiosity, did you build all of these from the ground up on your own? Or was there any LLM-gen involved, at one point or the other? Something about [this](https://github.com/egare0/claris/commit/dab05b5a4aed757bdb600e8f7d482cc8061bec08): > A clean, minimal, zero-dependency by default fluent logging framework. Features include module-level filtering, ANSI terminal colors, and _perfect_ output alignment. just seems off to me, for some reason. As do the [comments](https://github.com/egare0/zerec/blob/main/zerec/src/impls/primitives.rs) like: ```rust // ── u8 / i8 ─────────────────────────────────────────────────────────────── // ── u16 / i16 ───────────────────────────────────────────────────────────── // ── u32 / i32 ───────────────────────────────────────────────────────────── // ── u64 / i64 ───────────────────────────────────────────────────────────── ``` I wouldn't even know what character that is, much less be able to type it, in the spur of the moment. To have it _perfectly_ aligned throughout the whole module? I commend your ~~perfectionism~~ efforts. ---
**Author:** ![steffahn](https://sea1.discourse-cdn.com/flex019/user_avatar/users.rust-lang.org/steffahn/32/47569_2.png) [@steffahn](https://users.rust-lang.org/u/steffahn)\ **Post date:** [July 1, 2026, 8:57pm UTC](https://users.rust-lang.org/t/looking-for-code-review-on-my-4-small-crates/141053/3 "2026-07-01T20:57:25Z")
> [@marlez](#): > > I wouldn't even know what character that is ( [let’s check…](https://codepoints.net/analyze?q=%2F%2F+%E2%94%80%E2%94%80+u8+%2F+i8+%E2%94%80%E2%94%80%E2%94%80) ) > **[U+2500 BOX DRAWINGS LIGHT HORIZONTAL: ─ – Unicode](https://codepoints.net/U+2500)** > > ─, codepoint U+2500 BOX DRAWINGS LIGHT HORIZONTAL in Unicode, is located in the block “Box Drawing”. It belongs to the Common script and is a Other Symbol. ( ~\> [Box-drawing characters - Wikipedia](https://en.wikipedia.org/wiki/Box-drawing_characters) ) ---
**Author:** ![MOCKBA](https://sea1.discourse-cdn.com/flex019/user_avatar/users.rust-lang.org/mockba/32/41423_2.png) [@MOCKBA](https://users.rust-lang.org/u/MOCKBA)\ **Post date:** [July 2, 2026, 1:37am UTC](https://users.rust-lang.org/t/looking-for-code-review-on-my-4-small-crates/141053/4 "2026-07-02T01:37:24Z")
I am out of luck because implemented all your tools a year ahead. I need to slow down and relax, you will implement everything I need in the future. Just kidding. Good work, man. ---
**Author:** ![Jesper](https://avatars.discourse-cdn.com/v4/letter/j/49beb7/32.png) [@Jesper](https://users.rust-lang.org/u/Jesper)\ **Post date:** [July 2, 2026, 6:50am UTC](https://users.rust-lang.org/t/looking-for-code-review-on-my-4-small-crates/141053/5 "2026-07-02T06:50:25Z")
> [@marlez](#): > > I wouldn't even know what character that is, much less be able to type it, in the spur of the moment. To have it _perfectly_ aligned throughout the whole module? If you really want to, it can be automated - I have this in my nvim/init.lua config: ```rust vim.api.nvim_create_user_command("Div", function(opts) local text = "// -- " .. opts.args .. " " local fill = string.rep("-", math.max(0, 77 - #text)) vim.api.nvim_put({ text .. fill }, "l", true, true) end, { nargs = 1 }) ``` When I type :Div u64 / i64 it generates just such a line. Although I used '-', not "em dash", which seems to be one of the LLM tell tale signs. On par with decorating a README.md with colourful emoticons. ---
**Author:** ![Kyllingene](https://sea1.discourse-cdn.com/flex019/user_avatar/users.rust-lang.org/kyllingene/32/33899_2.png) [@Kyllingene](https://users.rust-lang.org/u/Kyllingene)\ **Post date:** [July 2, 2026, 7:45pm UTC](https://users.rust-lang.org/t/looking-for-code-review-on-my-4-small-crates/141053/6 "2026-07-02T19:45:11Z")
Note that this isn't an em-dash (`—`, U+2014); this is a horizontal box-drawing character (`─`, U+2500). I'm not sure how much LLMs like to use box-drawing characters for things like this. ---
**Author:** ![Jesper](https://avatars.discourse-cdn.com/v4/letter/j/49beb7/32.png) [@Jesper](https://users.rust-lang.org/u/Jesper)\ **Post date:** [July 2, 2026, 10:29pm UTC](https://users.rust-lang.org/t/looking-for-code-review-on-my-4-small-crates/141053/7 "2026-07-02T22:29:43Z")
You are right - you know your dashes - there are quite a few - they look similar, but there are small differences; In a terminal EmDash doesn't go all the way through a cell. Like it does here (browser). ```rust Ascii Minus U+002D ----------------- Unicode Minus U+2212 −−−−−−−−−−−−−−−−− EnDash U+2013 ––––––––––––––––– EmDash U+2014 ————————————————— Box U+2500 ───────────────── ``` ---
**Author:** ![marlez](https://sea1.discourse-cdn.com/flex019/user_avatar/users.rust-lang.org/marlez/32/52182_2.png) [@marlez](https://users.rust-lang.org/u/marlez)\ **Post date:** [July 3, 2026, 9:54am UTC](https://users.rust-lang.org/t/looking-for-code-review-on-my-4-small-crates/141053/8 "2026-07-03T09:54:07Z")
> [@steffahn](#): > > [Box-drawing characters - Wikipedia](https://en.wikipedia.org/wiki/Box-drawing_characters) Huh. Definitely wouldn't be able to tell it was these little guys all along. DDG just failed to look it up altogether. Never used any in my own code either. Though I can see the aesthetic appeal, I suppose. Quite trivial to script/automate, as well. My LLM paranoia might be getting the best of me, lately. To the OP - in the spirit of an attempt to stick to the actual topic at hand: I'm _pretty_ sure half of the replies in this thread discussing box drawings and em-dash'es instead of your code _does_ imply that none of the responders were able to find anything of note to review, nitpick or give any worthwhile feedback about. Good job, so far. Keep up the good work. ---
**Author:** ![user16251](https://sea1.discourse-cdn.com/flex019/user_avatar/users.rust-lang.org/user16251/32/30527_2.png) [@user16251](https://users.rust-lang.org/u/user16251)\ **Post date:** [July 3, 2026, 11:06am UTC](https://users.rust-lang.org/t/looking-for-code-review-on-my-4-small-crates/141053/9 "2026-07-03T11:06:56Z")
The Rustdoc in these crates is definitely LLM prose. ---
**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/users.rust-lang.org/system/32/51372_2.png) [@system](https://users.rust-lang.org/u/system)\ **Post date:** [October 1, 2026, 11:07am UTC](https://users.rust-lang.org/t/looking-for-code-review-on-my-4-small-crates/141053/10 "2026-10-01T11:07:40Z")
This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.