trace!("TheBestTvarynka")

Rust Playground now supports multiple files! I wanted it for a long time. The implementation PR was landed around a month ago: https://github.com/rust-lang/rust-playground/pull/1240

Call for testing: Restricting trait implementability and field mutability: https://blog.rust-lang.org/inside-rust/2026/08/10/call-for-testing-impl-and-mut-restrictions/ rustup update nightly tl;dr: ❓ What is impl_restriction? The `impl_restriction` feature allows explicit restriction of the scope in which a trait may be implemented. The exact example from the blog post: #![feature(impl_restriction)] // The impl(crate) restriction prevents Foo from being implemented outside the current crate. pub impl(crate) trait Foo { fn method(); } And yes, it was possible before via sealed trait pattern (https://rust-lang.github.io/api-guidelines/future-proofing.html#sealed-traits-protect-against-downstream-implementations-c-sealed). The impl_restriction approach has two pros: 1. Cleaner code without workarounds. 2. The compiler can produce better error messages when the developer tries to implement such trait outside its crate ❓ What is mut_restriction? The mut_restriction feature allows explicit restriction of the scope in which a field may be mutated. Also an example from the blog post: #![feature(mut_restriction)] pub struct Bar { // mut(self) pub mut(crate) alpha: u8, } The mut_restriction feature can also be used with fields of enum variants and unions. Where this feature may be helpful: 1. You no longer need to define a getter method. When the field can be mutated only inside self, then it's safe to access this field directly (because it cannot be mutated from the outside). 2. Preserve an invariant: we can disallow unrestricted construction with struct expressions. The compiler will throw an error when you try to create a struct using a struct expression outside the specified scope. 3. Let me just cite the blog post: It can also work better with the borrow checker, which can track borrows at the field level and allow disjoint fields to be borrowed independently. More info: 🟡 RFC: https://rust-lang.github.io/rfcs/3323-restrictions.html 🟣 Tracking issue: https://github.com/rust-lang/rust/issues/105077

what it has to do with clrf it's always CRLF, except the times when it's always DNS

https://tbt.qkation.com/posts/cursed-story-1-crlf/ A little bedtime story for you 😊 Cursed story - a tiny story from my experience I wish had never happened and increases my cursed knowledge.

https://x.com/i/status/2084360919904083970

I just added an AI Policy to my blog: https://tbt.qkation.com/ai-policy/ PR: https://github.com/TheBestTvarynka/tbt/pull/36 I see a huge rise in AI-generated posts and blogs (which is expected, of course). I don't want to be confused with them. I don't see any value in the AI-generated post. But I see a value in the handwritten blog post. Every sentence you write on your own becomes a unique expression of yourself. Every sentence you write on your own becomes your creation in this world. A human is made to create, not to consume ❤️ Be an artist ✨

Finally, I have time to write a proper blog post. Here it is: https://tbt.qkation.com/posts/announcing-grafily-0-3/

Re: Kimi K3: Open Frontier Intelligence > Chip Design > As an early proof of concept, Kimi K3 designed a chip to serve a nano model built on its own architecture. In a single 48-hour autonomous run, K3 built, optimized, and verified the chip using open-source EDA tools on the Nangate 45nm library. Within 4 mm², the chip closes timing at 100 MHz and sustains over 8,700 tokens/s decode throughput in simulation, packing 1.46M standard cells, 0.277 MB of SRAM, and an INT4 MAC array with fused dequantization. A chip built by a model, for a model, reflects K3's long-horizon agentic capabilities. Absolutely wild. lukebechtel, 11 hours ago

Tomorrow I plan to start learning Chinese. Who is with me? 😁

I love using great products backed by Ukrainians. I feel some kind of pride or something 😊

If your disk isn’t critically struggling with available space, are you even #Rusting? (src)

How it works: 1. You manually add tags to photos using the built-in tagger (1st image). You can open tagger from the file context menu (Tag people option). (2nd image). 2. Every tag is linked to some note. In my case, every note represents a person. 3. Add…

Another interesting tool that I found in the Rust Ukrainian Community chat: https://niche.rs/ Rust type layout & niche optimization visualizer. You type any Rust type and it will visualize that type layout. Pretty interesting to watch and experiment. If I had known about the niche earlier, I would have used it to teach students about structure layout, padding, and related optimizations.

Found this in the Ukrainian Rust Community chat: https://coredump.digital/. One more collection of Rust questions. Hand-written questions from real Rust interviews - ownership, lifetimes, traits, the corners of unsafe. Daily drills target your weak spots. 🟢Questions are easier than https://dtolnay.github.io/rust-quiz/. 🟢 I tried only hard questions, and most of them are interesting. In some cases, the correct answer is obvious because the correct option is 4-line text and the incorrect one is one-liner 🙃. But it's still interesting. 🟢 Overall, I can recommend them 👍

If you solve puzzles on Lichees, you know that puzzles are taken from real life games. Lichess scans all games and searches for interesting moves to create a puzzle from. But did you know that you can query puzzles created from YOUR GAMES? 😳🍟 Fun fact. I played around 4k games on Lichess and the platform created as much as 1 puzzle: https://lichess.org/training/24nxU. It was played 72 times! 😎 That game was 4 years ago. Currently, I have ± the same rating. No progress in 4 years 😭 Here you can query puzzles created from games of any user: https://lichess.org/training/of-player

https://x.com/mitchellh/status/2074225453217505494 Mind boggling to me that I can make a thing faster and there's always people that ask "but why?" What kind of mentality is that? The pursuit of excellence does not need justification. Also, I find in so many cases, we can't know the impact of an improvement until we do it. Mitchell is so based. If you can make things better, make them better. I agree that we can't know the impact of an improvement until we do it. Make things better because they can be better and let the results naturally play out. Yes! The more I read his tweets/blog, the more I adore him. Fun fact. He donated $300k to the Zig Software Foundation in 2024 (Paid out in annual $150k installments over two years.) and $400k in 2026 ($200k per year split over two years).

image_2026-07-06_15-29-56.png

Finally, the Grafily plugin is usable. I love how it looks and works 🤩 In the screenshot above, you can see my direct ancestors 🙃

The grafily plugin is available in the Obsidian community plugins 🥳🥳: 🔘 https://community.obsidian.md/plugins/grafily

We don't stop playing because we grow old; we grow old because we stop playing. (George Bernard Shaw) I wish you to continue playing as long as you can 🙃 🤓🤓🤓