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
This media is not supported in your browser
VIEW IN TELEGRAM
😁4👎1
In Rust it's mostly "and also write a book". Doc comments are really good for most of the libraries on crates.io
👍3👎1
Forwarded from Ноунейм мемы
👍5😁2👎1
And Rust experiences "is a plus"😁
😁7😢3👍1👎1
Hah it's nice to see the project I worked at previously trending in crate of the week. Good job Qdrant team!
👍6👎1
Forwarded from pub ThisWeekInRust {}
Crate of the week: Qdrant

This week's crate is Qdrant, an open source production ready vector database/similarity search engine written in Rust. There are APIs available for Rust, Python, Javanoscript/Typenoscript and Go.
🔥6👎1
Not a problem anymore
🤩8😁4👎1
But you have to use a monad to print Hello World! 🌚
😁3👎1
Forwarded from Impure Pics
👍2👎1😁1
That's all you need to know about Rust governance btw. The RFC process sadly has been non-existent for many years already.
😢7👎1
Oof nice release - Rust 1.70

Many things stabilized:
- OnceCell
- IsTerminal
- Arc, Rc::into_inner

These are a few immediately useful for me.

It's a good break from all the governance drama
👍3👎1
A proposed ownership design for D Lang in an article published in 2009, which as you could guess predates Rust's ownership system - https://bartoszmilewski.com/2009/06/02/race-free-multithreading-ownership/

Though as the author himself notes on Twitter, Graydon Hoare when working on Rust might have also been aware of the papers that D Lang ownership proposal lists as references.
👍5👎1
And another slide by Graydon Hoare explaining the move semantics from way back, when Rust was only incubating. I like how from beginning they decided to make the terminology not too academic.
👍5👎1
This media is not supported in your browser
VIEW IN TELEGRAM
👎1
😁9👎1
Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022

TL;DR

For those thinking about getting started with Rust here Google Devs confirm and debunk some rumors about the language:

Rumor 1: Rust takes more than 6 months to learn – Debunked (1-2 month to be productive)

Rumor 2: The Rust compiler is not as fast as people would like – Confirmed

Rumor 3: Unsafe code and interop are always the biggest challenges – Debunked (interop is easy, macros and async are the hardest)

Rumor 4: Rust has amazing compiler error messages – Confirmed

Rumor 5: Rust code is usually of high quality – Confirmed (people feel that code written in Rust is usually of high quality by nature)
👍8👎1🔥1😁1
Interesting trick, but there are usually easier ways to do typechecks during macro expansion in more specific cases
👎1