Falell

We should know shortly, the PR to fix this will presumably be paired a crater run, a build of the entire public crates universe.

This was my first question too, I don't see anything addressing e.g. the cyclical arc example from the original 'spawn' conversation.

It seems like you have to auto-propagate !Forget, and then make 'anything that be used to logically implement forget', probably most importantly things like Rc take a Forget bound and do it at an edition boundary? But the link mentions none of that...

Maybe a typo for To Be Quite Honest?

The kind of people GP is referring to refuse to actually learn from this. I've had several coworkers over the last 15 years that absolutely refuse to 'learn to fish'.

I think it shows exactly the opposite of the second. Even with the availability of checklists, and instructions to use them, people won't and don't actually use them consistently.

'With enough eyes, all bugs are shallow' and AI is an automatable eye that looks at things we can tell nobody has seriously looked at before. It's not a panacea, there will be lots of false positives, but there's value there that we clearly aren't getting by 'just telling humans to use the tools available'.

See also: modern practices and sanitizers and tools and test frameworks to avoid writing memory errors in C, and the reality that we keep writing memory errors in C.

Fun. 2.2 loads a blank screen for me, all previous levels were fine and 2.3 loads. Windows, Firefox 149.

Edit: Confirmed fixed.

Firefox has all of this except the date. `about:config` lists all config values, values in bold do not match their default or do not exist by default, values can be reverted with one click, and there's a checkbox to filter out unmodified items.

"worse is better", the fact that a great ecosystem has grown does not necessarily mean the language and its tools are great.

Personally, I find the lack of static types makes maintenance a nightmare, and think the build and deployment situation is miserable.

Credit cards have by far the best in-person UX of the options that I am presented, tap my card or phone and leave and they're accepted everywhere in practice (my debit card is not).

The 'cardholder can always reverse any charge' behavior is also nice once every few years.

Not a direct compiler optimization, but consider memcpy() vs memmove() as an example. If you know two regions of memory do not overlap you can call memcpy() for a direct optimized copy, but if they overlap you must call memmove() and introduce an intermediate copy.

From the PR body...

> The cowardly handling of the recent RustConf keynote fiasko...

The article shows that federation delivers data to Meta even if you personally don't use Threads, but I agree with your point.

If you want to control distribution of your data, don't join a federation designed to distribute data. Trying to blacklist nodes in a graph that you don't control is not a solution.

Information wants to be free, if you post something to a social graph assume everyone in the graph can see it forever.