frabert

I'm curious to understand which part you think is particularly interesting. The compiler clearly knows which variables are declared in what scope, so what's mysterious about figuring out which values need to be captured?

Haha this is bizzarely specific to my back-of-the woods brain. Feels like something that would be super relevant to someone in San Francisco but not as much to me

I think it means you can't assign to unbounded names, you must either declare with var for global, or let/const for local

Sorry, it was published early and we have to wait for some approval checks to clear

This has been a sore point in a lot of discussions regarding compiler optimizations and cryptographic code, how compilers and compiler engineers are sabotaging the efforts of cryptographers in making sure there are no side-channels in their code. The issue has never been the compiler, and has always been the language: there was never a way to express the right intention from within C (or most other languages, really).

This primitive we're trying to introduce is meant to make up for this shortcoming without having to introduce additional rules in the standard.

You can do the same with regular, non-embedded programs in a debugging session

> vibe coding is like a conductor orchestrating a symphony, fast but a little bit low quality

The hell is this supposed to mean lol

MSAA actually does, it stores more information per pixel using a special buffer format

Last time I checked, embedding Lua in C or C++ was _way_ easier than embedding Tcl

Or Barbra Streisand

It really do be like that sometimes

The Faust environment maybe?