Awful Rust snippets for fun and profit
Статистикаseen something awful and want to post it here? send it to @goldsteinq
- Последний пост
- 20 мар. 2025 г.
- Последнее чтение
- 13 авг.
- Постов за неделю
- 0
- Всего постов
- 20
- Тип
- открытый
- Язык
- английский
- В каталоге с
- 13 авг.
- 1/24сутки в ленте
- —
- 1/48двое суток
- —
- 1/72трое суток
- —
Оценка по просмотрам недавних постов: пост набирает почти всё за первые сутки.
Посты
answer and explanation will be posted tomorrow, please no spoilers in the comments
answer and explanation will be posted tomorrow, please no spoilers in the comments
видео или голосовое, без подписи
видео или голосовое, без подписи
increment a counter and get its value in a single expr playground thanks to @Kolsky and @feedable for showing me this!
notably, this does not compile playground
mixed-site hygiene might be surprising original blogpost (read it, it’s cool!) playground thanks to @alexpyattaev for suggesting this!
inherent method resolution doesn’t use i32 fallback on conflict, but trait method resolution does playground (I don’t think this is documented anywhere, but feel free to correct me) thanks to @Kolsky for suggesting this!
inherent method resolution doesn’t use i32 fallback on conflict, but trait method resolution does playground (I don’t think this is documented anywhere, but feel free to correct me) thanks to @Kolsky for suggesting this!
https://purplesyringa.moe/blog/the-rust-trademark-policy-is-still-harmful/
Awful Rust snippets for fun and profit pinned «I’m sorry, but we seemingly need to do the same exact thing again the new draft is somewhat better, but it still has at least two issues: — it requires explicit approval to host events that are not free to attend, which includes even non-commercial events…»
so, a quick PSA moment The Rust Foundation (not to be confused with The Rust Project, who actually develop Rust) is currently planning to put up trademark policies that are so restrictive that this channel would be affected. essentially, they want to prohibit…
macros can close over their environment, “breaking” hygiene playground I’d like to give a link to documentation here, but I don’t think this is actually documented anywhere? neither reference nor TLBORM mention it as far as I can see UPD: ferrocene specification
macros can close over their environment, “breaking” hygiene playground I’d like to give a link to documentation here, but I don’t think this is actually documented anywhere? neither reference nor TLBORM mention it as far as I can see UPD: ferrocene specification
cyclic associated types are okay under lazy normalization / next solver (you need ?Sized though, otherwise it tries to prove Assoc: Sized and fails) godbolt tracking issue
mixed-site hygiene might be surprising original blogpost (read it, it’s cool!) playground thanks to @alexpyattaev for suggesting this!
my fix for this problem was merged and will be stable in rustc 1.81, unless something goes wrong https://github.com/rust-lang/rust/pull/123043
iex by @purplesyringa automatically adds its attribute to the docs by injecting a <style> tag code link
видео или голосовое, без подписи
iex by @purplesyringa automatically adds its attribute to the docs by injecting a <style> tag code link