mbel

Or we’re just getting used to it.

Unless your code targets some exotic architecture, like idk x86.

Yeah, totally, just one more year.

Nobody would say „trujący wąż” (poisonous snake) or „jadowity grzyb” (venomous mushroom). The distinction is similar to English. There are exceptions and contexts where it can be used interchangeably but arguably the same is true for English.

Not really, we have both „jad” (venom) and „trucizna” (poison).

The primary use case that I can see is following: you use your second phone — the communicator — to chat, while watching endless stream of tiktoks/reels/shorts on the first one.

> In terms of CPU? The other way around.

That depends on your architecture and access pattern. In case of sequential access, packed bools may perform better due to arithmetic being usually way cheaper than memory operations.

> It’s less simple than many systems languages because it has a very strong type system.

I don’t think that’s the case, somehow most ML derived languages ended up with stronger type system and cleaner syntax.

In this case there is both time a distance limit to the gesture. If the gesture is too fast the switcher won’t appear even if the distance was long enough.

That said, personally I’ve always found the gesture navigation very intuitive.

It feels like a stretch to call this a parser. It’s looks like a typical lexer?

Probably the compilation time is better than it would be with LLVM. On the other hand I doubt that codegen and therefore performance is on par with LLVM.

Definitely a weird thing to advertise.

This is mostly an issue with MSVC which refuses to become compliant with c99 standard. Their support for c11 and c17 also has some gaps around features that were introduced in c99.

Most popular languages would prevent this. In this case it’s as simple as having more sensible reader API than sscanf in standard library and forcing variables to be initialized.

To be honest the implementation looks surprisingly readable… at least compared to other horrors like the standard library implementation.

While there are some new rules regarding arguments naming, the new syntax doesn’t feel more complex than the default lambda syntax.

So all in all I would say the most horrifying thing here is the fact that the language allows such extensions in the first place ;)