yaglo

Because they swapped some characters like \ to /, if I remember correctly.

1. Every class/method/function/whatever declaration is an API, doesn't matter if it's internal or which language it's written. 2. Why do you think it's better? It looks like it tries to cater to everyone, and leads to inconsistent API usage and requires teams to agree on linting rules and use tools to enforce consistent coding standards. 3. It's a tool for _you_ to design good APIs that are clear. Languages without named arguments don't give you this tool.

> So does renaming a label.

In languages without this feature, any renaming breaks the API, unlike the ones with distinct internal and external names. This is not the same.

Within Xcode, you don’t really need it because you’re already running with a debugger when you launch your program.

Yes, you can evaluate Swift code in LLDB. See https://stackoverflow.com/a/71882942

It’s a nicer experience during development out of the box, without having to do anything manually.

Swift Backtracing is not only about the symbols, it’s also interactive and lets you attach the debugger after the process crashes, which is neat.

The best part of is that you can get all this goodness even without having Swift code in your codebase.

Just link your C++ (or whatever) project with The Swift runtime (swiftrt.o and libswiftCore.so), and there you have it without writing any Swift.