There is a warning. IIRC it says "are you sure you want to discard all changes? This action is unreverisble". In the context of version management. Creating a file is a change. And just below the button to discard all changes is the list of changes. In that list he could've seen 3000 changes of the type "file creation", when you discard a file creation, it means to undo the creation, which is a deletion.
The button days what is going to do. There is a warning about what it's going to do. And there is a list of the exact changes it's going to undo.
The only way to avoid this from happening is to not have the button exist. In that case, the users that actually want to discard all changes would be unable to do so.
I don't even know why people ITT are blaming the IDE and completely ignoring this.
When you learn git, you do so on a dummy project, that has 5 files which are 10 characters long each.
An IDE is not made so you can't break things, it is tool, and it should let you do things. It's like complaining that Linux will let you delete your desktop environment. Some people actually want to delete your desktop environment. You can't remove that option just because someone can accidentally do it by ignoring all the warnings.
And unfortunately, this means that WG21, the C++ committee, has to take action because people are demanding it
Why does this mean that they have to take action? Why do they need to make C++ memory safe?
C++ was not designed to be memory safe. If you try to make C++ memory safe, you'll have to break retro compatibility. If you're going to break retro compatibility, can you say it's still C++? Or another language called C++2? At that point, why not just use another language that was designed from the start to be memory safe?
The action that should be taken is to completely avoid starting any new project in C++, and let the language die. A programming language is nothing more than a tool, once the tool no longer works, you search for another that does.
C++ should go the way of fortran and cobol. The only development of C++ should be done is to maintain existing huge codebases that would be too expensive to rewrite.
I have had many mouses. Most of them broke the side buttons. The scroll wheel usually lasts as much as the side buttons. After that. The left/right main buttons fail.
I have never had a mouse with a broken sensor though. I would look for solutions in the software (calibration and settings). But it's not impossible that it's broken.
You can just use an unsafe block though. Or make a thin wrapper that is just safe functions that inside just have an unsafe block with the C ABI function.
Even if rust had a stable ABI, you would still need that unsafe block.
I'm not so sure that dynamic libraries always reduces the size. Specially with libraries that are linked by a single binary.
With static libraries, you can conditionally compile only the features you're gonna use. With dynamic libraries, however, the whole library must be compiled.
EDIT: just to clarify, I'm not saying that static libraries result always in less size. I'm saying that it's not a black and white issue.
Editor/IDE, whatever. People claim both about jetbrains.
If you want a purely editor-thing:
Whatever vscode does with Ctrl+D (I don't know the name). Ctrl+D is probably the hotkey I use most in vscode (probably more than Ctrl+S), yet CLion doesn't have that. I've searched multiple times the whole settings for it.
Those two examples are just the ones that most recently occurred to me, it has a lot more issues. For example the lack of a staging area. You can't "git stage" in CLion.
And I don't think that the git integration is free from criticism. Git integration is one of the most important features of IDEs. It's absolutely valid to criticize it.
The autoformatter also doesn't work correctly when developing in remote. Which means that unless I want my PRs to have thousands of lines of whitespace changes, I can't use the auto formatter.
Now I don't know if this is a CMake issue or CLion. But at one point It was "#include"ing a struct from a header file I had deleted 1 hour previous to the build failing. The only way to fix that was to create the file again and delete it again.
These complaints might seem small. But put together they are hours of wasted time that you don't expect from the "best" of something.
Don't need to go all the way there. I always heard that jetbrains make the best editors. Yet when my job forced everyone to use CLion I saw that it was just a lie. The editors aren't good, they are just expensive.
There are 2 easy examples:
Remote developing sucks. Loading a remote cmake project takes ages. Yet if you remove the temp directory it's almost instantaneous. Except when you do it too often and clion refuses to sync the files, then you're fucked because there isn't a "sync" button, it only happens automatically.
The commit log is awful. It doesn't by default show you the commit/branch you've checked out, it shows the chronologically most recent commit. There's no "go to checked out commit" button either, you have to write the hash in the search field. Which btw the search is trash. If you write 6 of the characters of the hash it shows "there are no results", yet when you write the 7th, suddenly your commit appears.
The thing about UB is that many optimizations are possible precisely because the spec specified it as UB. And the spec did so in order to make these optimizations possible.
Codebases are not 6 lines long, they are hundreds of thousands. Without optimizations like those, many CPU cycles would be lost to unnecessary code being executed.
If you write C/C++, it is because you either hate yourself or the application's performance is important, and these optimizations are needed.
The reason rust is so impressive nowadays is that you can write high performing code without risking accidentally doing UB. And if you are going to write code that might result in UB, you have to explicitly state so with unsafe. But for C/C++, there's no saving. If you want your compiler to optimize code in those languages, you are going to have loaded guns pointing at your feet all the time.
I recently came across a rust book on how pointers aren't just ints, because of UB.
fn main() {
a = &1
b = &2
a++
if a == b {
*a = 3
print(b)
}
}
This may either: not print anything, print 3 or print 2.
Depending on the compiler, since b isn't changed at all, it might optimize the print for print(2) instead of print(b). Even though everyone can agree that it should either not print anything or 3, but never 2.
If you want to use instructions from an extension (for example SIMD), you either: provide 2 versions of the function, or just won't run in some CPUs. It would be weird for someone that doesn't know about that to compile it for x86 and then have it not run on another x86 machine. I don't think compilers use those instructions if you don't tell them too.
Anyway, the SIMD the compilers will do is nowhere near the amount that it's possible. If you manually use SIMD intrinsics/inline SIMD assembly, chances are that it will be faster than what the compiler would do. Especially because you are reducing the % of CPUs your program can run on.
Spaniard here. Not only does my company not pay me for lunch time. It also demands it to be at least 30 minutes long. How is it even legal to force my unpaid time to be a minimum amount?
There is a warning. IIRC it says "are you sure you want to discard all changes? This action is unreverisble". In the context of version management. Creating a file is a change. And just below the button to discard all changes is the list of changes. In that list he could've seen 3000 changes of the type "file creation", when you discard a file creation, it means to undo the creation, which is a deletion.
The button days what is going to do. There is a warning about what it's going to do. And there is a list of the exact changes it's going to undo.
The only way to avoid this from happening is to not have the button exist. In that case, the users that actually want to discard all changes would be unable to do so.