flqn

Is this not more an issue with the proxy implementation? If it deferred to the proxied object's methods, would there be no issue with the proxy attempting to access its private fields?

Apologies in advance if I'm misunderstanding the purpose of proxies.

Euler angles are what that leads to gimbal lock. Constructing a rotation matrix from them inherits this issue.

Anarchy is not chaos, anarchy is the lack of top-down control.

Having a quick edit->build->run iteration time is important. Drop your dogmatic views on what makes a "professional" (hint: it literally just means someone who gets paid to do the work).

Nvim+plugins gives me pretty much all I need, and there's usually always some vi variant on any linux env I've had to use.

It's not unusual to spin up a local dev server in the same environment (or on the same machine, ie at localhost) as the tests. There's an argument to say these aren't "unit" tests but your definition of "unit" may vary.

ICEs don't detonate the fuel under normal operation; that's called "knocking" and can be extremely damaging to the engine.

I think the difference is that you did the inversion symbolically, not numerically. This is about numeric computation not applying algebraic manipulations.

Respiration

What a useless and jaded assumption that code written in the past is bad.

We've only been able to infer dark matter densities over galactic scales so I'm not sure that density applies at planetary system scales. It's like trying to use the density of iron to say where the atoms in a chunk of it are.

Pragmatism of decision is orthogonal to quality of execution :>

I think you are missing that const is insufficient for safe concurrency; it requires programmer discipline to ensure there are no shared mutable references.

Const also has no bearing on lifetimes. Constexpr/consteval do, but those objects always have static lifetime so it's sort of irrelevant.

Performance without safety sounds to me like "I'm doing the wrong thing, but faster!"

Getting a non-const reference out of a const object isn't undefined behaviour.

No, const can be added to objects at any declaration or callsite, meaning there can be many const- and non-const references to the same object within the same scope/thread/program/address space/execution context.

Const doesn't solve aliasing.

Accessing uninitialized objects is undefined behaviour, which traps in the constexpr context.

In a similar boat and I wonder the same myself. My current thoughts are that I've had mild executive function disorder for most of my life, and self-medicating has helped in the short term but perhaps caused longer-term effects due to building a dependency on it.

A c++ lambda is a struct with a call operator. The destructors of captured objects are appropriately called when the lambda's lifetime ends.

Managing the lifetime of referenced objects is something you always have to worry about in c++ anyway, lambdas don't change that.

The abstract clearly states that the paper is meant to highlight that selectively using and interpreting data can lead you to make bad hypotheses and conclusions.

This is not an article that is seriously advocating for cigarrette use.

EDIT: seriously, it's against the guidelines to ask "did you even read the article" but for real man, it's like the third sentence in the abstract.

Fusion has no possibility of an uncontrollable runaway reaction

I'm sceptical about the value proposition of this without seeing much more than a simple example that offers little over existing hypermedia+json/csv practices.

If a compact columnar representation is what you're after to avoid having to repeat every field name in an array of objects (which CSV is good for) but you don't want to give up the ability to include metadata in your JSON, there are a ton of different ways for structure your document to solve this issue without inventing new document formats.

Also this example is unclear (possibly ambiguous?); how is "int" as a type for the "age" column distinguished from "street", "city", etc as what I assume are field names?

The mass comes from binding energy, not kinetic. The binding energy is potential energy in the gluons and their interactions with the quarks.

Signed integral operations are often faster too, since the well-definedness of unsigned overflow can require additional instructions esp. if the width of the unsigned integral is not the same as the architecture word width.

Is this page completely broken for anyone else? After the fade-in animations, the whole page vanishes. Using Chrome, btw.

What would you rather have: an object of value potentially outside your domain and an expensive boolean function saying if it's ok that you need to apply everywhere just to be sure, or a method of producing values that you know are always within your domain which you have to apply just once and no expensive boolean function?

If the copy behaviour is that different between the two cases it should be two different classes.

Both latches and barriers can be implemented with a counting semaphore sure. C++20 provides one of those too along with these abstractions.

This, so much. Every branch or decision point in either the domain model/flowchart/spec/etc or implementation should be carefully considered. This applies doubly so to error handling. Also, try to make the code paths look like or at least be recognisable by the spec. Try to keep one mental model of what happens that the team all share.

That implies the amount of training is the only factor. It may be that new architectures or training methodologies could be developed to reject large swathes of these types of advesarial examples. Though of course, if adversarial training is used avdersarial examples will obviously exist at some level, and so the arms race continues.