Viewing profile — sgsjchs

> dictionary based compression That corresponds to PCFG models.

The first LZ-step pretty much directly maps to BPE tokenization in LLMs.

Make multiple nodes do the same job, compare results.

You have it backwards. This formal game-theoretic notion of fairness acknowledges that power disparity exists and that having less power than your counterparty allows them to infli…

Does it really matter that English is not as precise if the agent can make a consistent and plausible guess what my intention is? And when it occasionally guesses incorrectly, I ca…

It's the other way around.

The trick is to provide dense rewards, i.e. not only once full goal is reached, but a little bit for every random flailing of the agent in the approximately correct direction.

I, too, enjoy the craftsmanship, but at the end of the day what matters is that the software works as required, how you arrive at that point doesn't matter.

> I still don't understand this decision. Variable declaration `T v;` means "declare `v` such that expression `v` has type `T`". Variable declaration `T *p` means declare `p` such …

But in C that's just syntax sugar for pointer math.

You very rarely would actually want scalar types which don't map directly to hardware supported ones anyway.

Why would you want to store arbitrary individual passwords instead of deriving them with on demand from the service name/domain and a common secret?

Indeed, the "valid but unspecified state" refers only to some types defined in the he standard library. It essentially means that you can only call methods which have no preconditi…

> No, the class can use a sentinel value internally only to mark moved-from objects. That's exactly where we actually started the conversation. The issue is that the "moved-from" s…

> Again, I don't see what this has to do with destructive moves. If you want a socket class that always refer to an open socket, you can already do that. Technically you can, but i…

> what difference would it make The same difference as making pointers always non-nullable and reintroducing nullability via an optional wrapper only when semantically appropriate.…

You don't need optional in this case, the assignment would just destroy the old socket and immediately move the new one in its place.

> And what's the underlying value of such a default constructed socket? I assume it would be -1 resp. INVALID_SOCKET No, as explained, the default value would be the result of `::s…

Reopen by constructing and assigning a new socket.

In this case, I would want the address family and protocol to be statically known, so it would have default constructor. But for example, a file might not have one, sure. As for cl…

If the moves were destructive, I'd design it to have the default constructor call `::socket` and destructor call `::close`. And there wouldn't be any kind of "closed" state. Why wo…

A socket.