Type Driven Thoughts 🦀 – Telegram
Type Driven Thoughts 🦀
230 subscribers
62 photos
1 video
117 links
Thoughts, jokes, articles about software engineering, type systems, sysprog, shiny new languages and of course Rust.

A personal channel of @eadventurous
Download Telegram
CTO of Azure
👍5
An updated mdbook about Rust macros - https://github.com/Veykril/tlborm

I remember using the original one (2016 edition) when studying them, it's cool that Rust team is finally continuing this effort
This year I will be participating in RustCon as a speaker with a couple of topics I was closely tracking in the past several months. So don't hesitate to join the conference online or offline😊. The video recordings will probably be available after a 6 month delay.
🔥3
RustCon все ближе, а у нас на сайте все больше согласованных докладов. Сегодня знакомим вас с Егором Ивковым из Qdrant и его докладом «New and upcoming Rust language features»

Доклад будет особенно полезен, если у вас уже есть опыт в работе Rust и желание узнать, в какую сторону язык будет развиваться дальше. Егор обещает разобрать свежие семантические и синтаксические изменения в языке Rust (например, Const Generics и Generic Associated Types). Потом вместе обсудим, где и для чего их можно использовать, сравним, как они соотносятся с дизайном других известных языков.

А еще посмотрим на широко обсуждаемые сейчас Generic Keywords и Context и поговорим про такую острую тему как Higher Kinded Types и нужны ли они расту.

В этом году RustCon пройдет в онлайн и офлайн-форматах. Посмотреть другие доклады программы и купить билет по ранней цене можно на сайте.
🔥5
Rust 1.65.0 released!🥳

Main features
- Generic Associated Types
- let ... else ... statements

https://blog.rust-lang.org/2022/11/03/Rust-1.65.0.html
🔥41🎉1
Should Higher Kinded Types be added into Rust?
Final Results
51%
Yes
12%
No
29%
Not certain
8%
Not using Rust
Forwarded from ozkriff.games 🦀 (ozkriff🇺🇦)
# Google: Memory Safe Languages in Android 13

https://security.googleblog.com/2022/12/memory-safe-languages-in-android-13.html

> There are approximately 1.5 million total lines of Rust code in AOSP ... To date, there have been zero memory safety vulnerabilities discovered in Android’s Rust code.
> ...
> In general, use of unsafe in Android’s Rust appears to be working as intended. It’s used rarely, and when it is used, it’s encapsulating behavior that’s easier to reason about and review for safety.
> ...
> As the amount of new memory-unsafe code entering Android has decreased, so too has the number of memory safety vulnerabilities. From 2019 to 2022 it has dropped from 76% down to 35% of Android’s total vulnerabilities. 2022 is the first year where memory safety vulnerabilities do not represent a majority of Android’s vulnerabilities.

/r/rust discussion
🎉4👍1
The one I've been waiting here for is definitely hint::black_box that recommends to compiler to disable optimisations in a particular place.

Had a few actual cases for this, when the code which is meaningful is optimised away.
👍3
Forwarded from ozkriff.games 🦀 (ozkriff🇺🇦)
# Rust 1.66.0

Highlights:

- Explicit discriminants on enums with fields
- core::hint::black_box
- cargo remove
- ..=X ranges in patterns

https://blog.rust-lang.org/2022/12/15/Rust-1.66.0

/r/rust discussion
👎1
Killer feature
😁7👎1🔥1
You don't need to debug if there are no bugs. Any valid Rust syntax is guaranteed to be bug free and do exactly what you intend for it to do. The people that still debug are the ones who haven't figured out that smashing your face on the keyboard and pushing straight to production is perfectly valid in the Rust context.

From reddit
👎1
This media is not supported in your browser
VIEW IN TELEGRAM
3👎1
This is what I feel has happened to the Rust core and other teams. Passionate people - who were originally there - burned out and are slowly being replaced by community members that just care for prestige.

(The screenshot is from a non-related to Rust topic)
👎1😱1