Joern Barthel

Made the example more simple and more concrete. Does that make sense? Furthermore: does it make sense to include a macro in axum that makes such a pattern more ergonomic...

Not entirely sure how the consensus process here works - happy with the PR being merged but I can also rework it into documentation. Let me know (or merge)! Regarding...

Feel free to drop or squash the linebreaks commit. I found (the lack of) them confusing.

(deleted my previous comment) My current thinking about a naming convention for mobile + web and fullstack that feels a bit more intuitive for me is the following: - `api`...

v18 is [out](https://github.com/google-gemini/gemini-cli/releases/tag/v0.18.0) and has [the fix](https://github.com/google-gemini/gemini-cli/pull/13338) in it. Regardless my current Zed is stuck in "loading" when using the Gemini Agent, so maybe it's not fully there?

Very late to (this) party but introducing the opposite of "spoofable" would allow the possibility of differentiating between a bunch of options of _why_ a value is "safe" (also avoids...

Most simple version would introduce approx the following changes: - add futures as gated dependency - add [smol](https://github.com/smol-rs/smol) as dev dependency for tests - convert the primary loops in signed...

Like this (naming tbd.)? ``` #[derive(Default)] struct ReadCtx { buf: [u8; 1], forward: bool, result: u64, shift: i32, } impl ReadCtx { fn unsigned(&mut self) -> Option { if self.forward...