#prog #article
The bottom emoji breaks rust-analyzerbecause ra is fucking vanilla
Спойлер: rust analyzer по итогу не причём, виноват другой софт .
The bottom emoji breaks rust-analyzer
fasterthanli.me
The bottom emoji breaks rust-analyzer
Some bugs are merely fun. Others are simply delicious!
Today’s pick is the latter.
Reproducing the issue, part 1
(It may be tempting to skip that section, but reproducing an issue is an important p...
Today’s pick is the latter.
Reproducing the issue, part 1
(It may be tempting to skip that section, but reproducing an issue is an important p...
😁2👎1
#prog #go #article
All your comparable types
Или как костыли реализации привели к костылям в спеке (а заодно неплохая иллюстрация того, почему для нормального дизайна дженерики должны быть в языке с самого начала)
All your comparable types
Или как костыли реализации привели к костылям в спеке (а заодно неплохая иллюстрация того, почему для нормального дизайна дженерики должны быть в языке с самого начала)
go.dev
All your comparable types - The Go Programming Language
type parameters, type sets, comparable types, constraint satisfaction
#prog #go #article
Go'ing Insane
Сборник жалоб на Go в пяти частях (+ одной бонусной). Часть претензий не актуальна из-за появления дженериков, но остальные вроде и сейчас справедливы.
Go'ing Insane
Сборник жалоб на Go в пяти частях (+ одной бонусной). Часть претензий не актуальна из-за появления дженериков, но остальные вроде и сейчас справедливы.
Jesseduffield
Go'ing Insane Part One: Endless Error Handling
I’ve been using Go for a few years now, mostly in my open source project Lazygit. In my day job I use Ruby and Typescript, and I’ve also spent some time with Rust. Each of those languages have design quirks that can grind a developer’s gears, and although…
😁1
#prog #cpp #article
The surprisingly high cost of static-lifetime constructors
Conclusion: Avoid any use of X-macros that results in lots of static-lifetime data with non-trivial construction (or destruction) semantics. And remember that any use of
The surprisingly high cost of static-lifetime constructors
Conclusion: Avoid any use of X-macros that results in lots of static-lifetime data with non-trivial construction (or destruction) semantics. And remember that any use of
initializer_list<T> also implicitly creates static-lifetime data of type T!quuxplusone.github.io
The surprisingly high cost of static-lifetime constructors
I was looking at HyperRogue again this week (see my previous post).
It has a really nice localization framework: every message in the game can be translated just
by adding a lookup entry to a single file (like, for the Czech translation, you add entries
to…
It has a really nice localization framework: every message in the game can be translated just
by adding a lookup entry to a single file (like, for the Czech translation, you add entries
to…
Forwarded from Сельский блог 🍁
Штож, всем доброй ночи. Вот вам тема для размышления перед сном. Высыпайтесь.
❤9🤮5❤🔥3🤔2💩1