sixfiveotwo

Why program in C++ if you don't use any of its features? You're just writing C in disguise.

Okay, vtables in 2kb code space?

> I can assure you that when writing code for microcontrollers with 2 kilobytes of code space, we don't include a 14 kilobyte string formatting library...

I'm pretty sure you wouldn't use C++ in that situation anyway, so I don't really see your point.

Hmmm, no.

https://stackoverflow.com/questions/31912781/why-doesnt-the-...

> And for public channels, E2E is pointless - everyone can see it anyway.

Shouldn't it at least provide some guarantee that what you receive is what was sent?

What you guys probably want to do instead is get to a common definition of what a typo is. Personally, I understand it as a typographic error, which is a fancy way of saying a spelling mistake (a mistake on a letter), not a mistake where one use a word for another.

Maybe you meant the latter?

Of course, the illness cannot get worse without the virus first infecting a cell, and then replicating in that cell to infect other cells in the body, and then potentially infecting other hosts; that is how a virus works, right?

Now, if replication is stopped, AND the body is able to destroy the first infected cell, then the patient is cured, but otherwise?

I guess that even if the body's immune system cannot get rid of that "patient cell zero", it is quite possible that a 6 month period is enough for the cell to die from the virus.

I do not have any medical training though, so please correct me if I am wrong.

You should read the company blog post linked in the article.

I didn't mean that it should be made into a bottom type, even though it sort of looks like it on the surface.

I think the original idea was that void meant "unknown", not "empty" or "non-existent": It was all about whether values could be allocated or not (the wart mentioned above). A plain void variable cannot, but a void pointer can be allocated. For functions, they just reused the keyword to mean "no return value" or "no arguments".

Sorry, I wasn't clear enough: I meant that void is not just a mix of the unit and bottom types, it is also in used for unspecified (unknown actually) types.

> void is the unit type. The fact that it is not constructible is a wart of the language, inherited from C. > A function returning bottom cannot return, yet void foo() {} can.

Or you could say it the other way, that it is the bottom type, and the fact that it can be used as the unit type for returned values is a wart of the language. Furthermore, void* isn't a pointer of the unit type, it's a type for pointers to undefined/unspecified value types.

In this encoding of the problem, the graph is fully connected, the edges indicate the state of a connection (ie. friendship) between 2 users, and the goal is to check that there is either a chain of 2 "connected" edges (A to B and B to C for any A,B,C in the nodes) or 2 "disconnected" edges, which indeed isn't easy to do the tedious way.

The crucial property here is the symmetry between connected and disconnected edges: for any given configuration, if it's difficult to check it on one hand, then it should be easy to do it on the other.

Thank you for the article, very interesting!

How is the copilot key recognized on OpenBSD? Does it appear like an extra Function key?

Thank you for your input, I stand corrected. So as I understand it, it works somewhat like the result type of rust (or ocaml), or the haskell either type, but instead of being parameterized, it is extensible, isn't it?

Well, perhaps a subset of it, since it also introduces concepts that do not exist in C (eg. exceptions).