trace!("TheBestTvarynka")

The last thing I did during my vacation: https://tbt.qkation.com/posts/genealogy-graph-positioning/ Tomorrow is a working day, but I want to take my backpack and go camping again 😭😭😭

Sorry for the undeleted (already deleted) spam in the channel chat 🙏. I was on a 3-day camping trip in the Carpathian Mountains 🙃

https://github.com/rust-lang/rust/pull/156882 😳☺️😍

🏪 Ваш особистий Google Chrome Hister — як Google, тільки для вашої власної бібліотеки документів і збережених сторінок (PDF, DOCX, TXT, Markdown тощо). Це не просто пошук за назвою документа, він індексує кожен документ, який ви додали, видобуваючи з нього весь текст та дозволяє шукати за ключовими словами або фразами, які містяться в цьому документі. Позиціонує себе як приватна пошукова система, з локальною конфігурацією, без телеметрії. Windows, Linux, macOS. Якщо у вас сотні різних навчальних лекцій, робочих документів, текстових файлів в різних форматах, і потрібно швидко щось знайти. Ви просто "гуглите" потрібне слово або фразу, яку пам'ятаєте і він знаходить всі ваші документи, які містять ці слова. Можете призначити його стежити за конкретною папкою, наприклад, там де у вас зберігаються документи, лекції та інші матеріали, і тоді всі файли, які ви закинете в цю папку, автоматично додаватимуться до пошукової видачі в Hister. #програми #навчання

👉 September 18, 2026 👈

Added AGENTS.md support: in a project with no CLAUDE.md, Claude Code reads AGENTS.md instead;

https://code.claude.com/docs/en/changelog#2-1-277 Finally. Now I'm wondering if it will read nested AGENTS.md files and .agents/ directory 🤔

I wrote the second post in a series about building and rendering genealogy graphs: https://tbt.qkation.com/posts/genealogy-graph-interactivity/

✅ The Hobbit ✅ The Fellowship of the Ring ✅ The Two Towers ✅ The Return of the King It was a long journey but I finished it. I have a lot to say. I will post my review soon 😌

https://blog.rust-lang.org/2026/08/21/enabling-next-solver-on-nightly/ 🥳🥳🥳

After nearly 4 years of active development, the next-generation trait solver is close to stabilization. We are enabling it by default on nightly to surface any remaining issues and plan to stabilize it in the next months.

The removal of the old implementation will unblock features such as Type Alias Impl Trait and Return Type Notation, allow us to add new implicit default trait bounds (e.g., Move and Forget), and enable us to fix the remaining type system unsoundnesses.

Even so, this already fixes a huge number of issues. As an underapproximation, we currently know of more than 200 issues on GitHub fixed by this change.

It's a huge step in the Rust language development. I hope to see this stabilized this year 🤞

Щойно побачив що про неї вийшла стаття на dou: https://dou.ua/lenta/articles/obituary-for-yuliia-zdanovska/ Якщо комусь цікаво, то в статті детально описане життя Юлії Здановської

Re: Firefox is now the last major browser that still supports uBlock Origin Support Firefox. F** Chrome. imagetic, 2 days ago

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

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/ 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 as 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. More cleaner code without workarounds. 2. The compiler is able to 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: ```rust #![feature(mut_restriction)] pub struct Bar { pub mut(crate) alpha: u8, }

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 😊

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 ✨

Since the Grafily 0.3.0 release, I have implemented a lot of important stuff. I decided to write a blog post about all improvements and fixes (with examples, of course). Ladies and gentlemen, to your attention Grafily 0.3.6: https://tbt.qkation.com/posts/grafily-0-3-0-0-3-6/ I don't even try to describe all the new features here on Telegram, because it's just impossible to do in a few sentences. Better go and read the blog post 😉