yoshuaw

Joined 12 years ago

Karma
682
Submissions
180
Member since
Sep 8
Be kind to people, be ruthless to systems.

Concurrent Computing ←

Programming Language Design ←

WebAssembly and Rust ←

u(๑╹ᆺ╹)

View on Hacker News

Recent submissions

Comment · 11 days ago
Return Type Notation (RTN) I believe is the big one blocked by the new solver. This is the primitive that makes it possible to add bounds to futures returned by async functions. This should look something like: `where <T as Trait>::method(..): Send`.

This is one of two remaining features needed to make Async Functions in Traits (AFITs) practical. Dyn dispatch support being the other missing feature, though that isn't blocked by the new solver.

Comment · 2 months ago
Niko Matsakis (T-Lang) has since also published a post on only-bounds: https://smallcultfollowing.com/babysteps/blog/2026/06/09/onl.... Sized hierarchy, Move, and Forget/Leak all share the same fundamental compat issues, so we're all pretty motivated to solve the underlying problems in a way that enables all the other features to be built on top.
Comment · 2 months ago
Comment · 3 months ago
One of my favorite quotes on this topic is:

"Type systems are just the parts of formal verification we've figured out how to make fast."

Comment · 3 months ago
Comment · 3 months ago
Comment · 3 months ago
My favorite base 10 clock is Neralie: http://wiki.xxiivv.com/site/time.html

> The Neralie clock has two groups of 3 digits, called the beat & the pulse. A beat contains 1000 pulses, and equivalent to 86.4 seconds. A day is 1000 beats, or a million pulses.

Comment · 4 months ago
Worse specs? Sure. Worse value? I don't think so. Worse accuracy? Perhaps not either.

A price of 30 EUR makes this sensor really easy to pick up. For the same price as one Aranet (~180 EUR) the typical household can place a sensor in every room of the house. Which provides far more accurate readings for the whole house than just one high-end sensor in one room.

Comment · 4 months ago
Comment · 4 months ago
Comment · 4 months ago
Seconding this. Writing .wast files by hand is kind of fun as a novelty, but it's in no way something I'd want to maintain interfaces in.

Declarative interfaces via the WIT format are so much more readable in comparison; I'm really happy that's the direction we took for the component model.

Comment · 4 months ago
Thank you!
Comment · 4 months ago
Hey everyone, we just published the announcement post for WASI 0.3 on the Bytecode Alliance blog:

https://bytecodealliance.org/articles/WASI-0.3

The current link is just the release notes and covers only the interface-level changes. The announcement post goes into more detail on what's new in WASI 0.3, how it differs from WASI 0.2, and includes examples.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton