Alona

💛+|💜

@lean-lang.org really lives up to its namesake as a gateway drug! :)

some should (or quite possibly has) write a thesis about how “sorry” sometimes is and sometimes isn’t an apology (esp in a UK/Canadian context)

tired: eternal september

wired: eternal hacktober

yeah, you should reduce any problem to SMT instead.

~~and also start writing cross-crate to let you eat-up all the perf wins~~

.o0O( i should finish the binary serialization format work )

I'm unreasonably excited about the upcoming cargo-semver-checks release: this month we put some points into "make it a joy to use and build."

- 3x faster at scanning very large crates
- its `cargo test` now takes 1min not 6-7min
- we gracefully handled a massive change in the rustdoc JSON format

just saw a take about how “worse” type systems were better because LLMs/agentic can’t handle expressive type’s the author is in dialogue with

they want the tools to just be able to run without interruptions from a system that can be correct

i hate how genAI is such a dimming of horizons everywhere

they’re making ai podcast summaries of podcasts about ai 😢😢

Welp... better apply now... better late than never

still wild to me how it's mostly unquestioned that "lexing" in a compiler is a separate stage (rather than an implementation detail of the parser) and yet "semantic analysis" can emcompass like 4 different passes

rustdoc-json finally has structured attributes, using an enum rather than a string. This should mean no more parsing by consumers, and `FORMAT_VERSION` breaking due to rustc refactoring: github.com/rust-lang/ru...

Tacit Kingdom would be a great name for a band (or a blog).

you kid, but github.com/uutils/coreu...

Unsoundness and accidental features in the #[target_feature] attribute Making Rust better for everyone while working on `cargo-semver-checks`

New blog post + cargo-semver-checks v0.42 is out ✨

I found some unexspected sharp edges in the `#[target_feature]` attribute. They are getting fixed (teamwork! 🤜🤛), and cargo-semver-checks now also has lints to save you from footguns!
predr.ag/blog/unsound...

this kind of dense, walkable control flow graph is illegal to build in most american compilers

also, the intersection of LLM and LLVM quite the acronym overlap

very cool, thanks for sharing.

it’s interesting how LLVM having formal methods to show correctness (alive2) makes this much more do-able, as you can fact check when the LLM says this this is a correct optimisation, and be confident without being an expert in LLVM

made the mistake of reading HN again, someone hit me with a stick

> is fortran a marxist? is APL a queer ally? is KDB+ my friend?

“postcard-from-the-future” would be a great library name if it wasn’t soo unwieldy in source code.

!!! but please call that postpostcard (or something) so there’s not horrendous confusion between postcard 2 (same wire format, api break) and postcard 2 (new wire format)

A terminal prompt: gh-aDotInTheVoid@dev-desktop-eu-1:~/rust2$

if rust is soo good, why didn't they make rus.. oh shit

last boost? i.e. the previous thing the retweeted in their timeline.

oil crisis queen? oil crisis tonight queen?

has anyone played molly house, especially more than a couple of times? i’d love to swap notes.

woot!!!!

Add a comment to `FORMAT_VERSION`. by nnethercote · Pull Request #142601 · rust-lang/rust This minimizes the chance of two PRs changing it from N to N+1. Fixes #94591. r? @aDotInTheVoid

@reduct.rs voice: How To Make Your Merge Conflict Work For You: The `// Latest feature:` story

github.com/rust-lang/ru...

blood work? i sure hope it does