Nadri’s musings

Many people want to know, precisely, which pieces of text are valid Rust programs, and for those that are, what they do.

In a recent post, I touched upon the "contexts and capabilities" feature idea; after more thought and exciting discussions with Boxy, Jana and others, there's a bullet we're tempted to bite: what if we just used plain old trait bounds?

Rust is very liberal in how it allows items (types, traits, functions, ...) to depend on each other and even themselves.

In my last post, I showed you how traits behave like passing a bundle of methods between functions, except automatically inferred by the compiler.

A common way to define equality in type theories, attributed to Per Martin-Löf, is as follows: a == b is a type with two parameters a and b, and it has a single constructor refl x with type x == x.

This article is part of an collaboration with the Rust Types team where we're looking into integrating these ideas into the Rust compiler to make it more robust and more correct.

The heart of Rust borrow-checking is this: when a borrow is taken, and until it expires, access to the borrowed place is restricted.

In a recent meeting, Niko proposed that we should add language features to enable desugaring more implicit things into valid Rust.

This blog post is part of the discussions around the Field Projections project goal.

Postfix macros is the feature proposal that would allow something.macro!