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?

This! Or, if you don't have geothermal heating but have an electric water heater, maybe temporarily increase the temperature it goes to: maybe it's normally set to go to 65C, then when you detect that you have negative prices and your batteries are full and your water already hot, maybe heat the water to 70C and store that little bit of extra energy as heat! If you have thermostatic valves in your bathrooms, you won't even notice the difference except by the fact that your water heater now can apparently hold a little bit more water than usual :)

https://boo-language.github.io/ The Boo language comes to mind as something similar

Yes, the game told me it was the preferred way and I followed the advice

The thing about Outer Wilds for me is that it's a game about exploration, but most attempts at exploration are punished (limited time frame, sands suffocating you, "ghost matter" kills...). They stuck with a "hard scifi" control scheme where you control your character in 6dof with inertia, which makes some things unnecessarily hard and did not (IMO) add anything to the game itself. The things you interact with in the world are also annoying to use, like the machines where you need to slide a ball around by locking it with your sight... Just let me press a button already!

I would consider a synth digital if it contains a DAC or at least a DCO, otherwise you'd say that relaxation oscilators are analog too :)

Cool project! Why do you call it digital though? The oscillator is analog

I enjoy abusing C++ templates for fun and for the challenge

I once (tried?) to implement some form of refinement types using C++17 templates as my BSc thesis: https://github.com/frabert/bsc-thesis

It's more or less as horrific as you can imagine...

I think the article's author may have seen the cs.DS classification on the arxiv and assumed it meant Data Science instead of Data Structures

Finally! I've been making the joke "put Linux.js in a PDF so I can run Linux, inside a PDF, inside a browser, inside Linux, inside a PDF, inside a browser, inside Linux" for far too long...

Let's say you have an interface 'Reader' with methods 'Read' and 'Close'. In a world where no interfaces exist, every user of a different implementer of this interface would need to know exactly which 'Read' and 'Close' implementations to call, and possibly generate different code for it.

In order to make this mechanism generic, you can instead say, "every implementer of the 'Reader' interface has a pointer as its first field, and that pointer leads to an array of two elements: the first element is a pointer to a 'Read' method, the second to a 'Close' method."

This way, the user of a Reader knows nothing of the internals of each implementation, other than how to find its methods

I guess we can't effectively modulate it fast enough to make it practical for communication

I long for the day when my liver can also act as a particle accelerator

If you don't think it's a good thing to recognize your own mistakes and try to warn others about them, then I don't think I have anything else to discuss.

I was talking "fairness" from the point of view of the EU in this case, and it is the exact sense that you are delineating in your addendum at the end of the comment.

It is "unfair" that a country gets to run circles around me because it completely ignores things that I consider important rights that my citizens fought for -- sane working hours, right to have my data kept to myself, right to express discontent against the government