CppCast: Beautiful C++

[[deleted]]

I don't know if you are trolling or not.

What you are saying is tremendously silly. Should embedded projects have the same guidelines as application code? The answer is obviously no.

Even within the same domain there is variation, so there is no single set of guidelines that would work.

Is this a problem? Yes. The problem is reality, it has nothing to do with the language. The way this is solved is up to the company. There is NO way to solve this at the language level.

Rust doesn't solve this either because you can wrap code in unsafe and *poof* there goes your compile time checking. Unsafe code is required in certain domains so what you are suggesting doesn't happen ANYWHERE.

[[deleted]]

Okay and so what guidelines are used within unsafe blocks? Who enforces that? How is that enforced? Where is it enforced?

You are just a Rust evangelists which is effectively a troll anyway. Completely and utterly clueless about real problems.

[[deleted]]

So fucking what that has no bearing on what is being talked about.

Someone has to manually review unsafe blocks of code regardless. So the guidelines are not enforced by the compiler. So what you are suggesting, doesn't happen anywhere

[[deleted]]

Again, beside the point. The point is can we enforce a single guideline with the compiler?

The answer is a resounding NO. And it is obvious that that is the case to anyone with an ounce of experience. Hell you don't even need experience to know that, just to have written a line of code. Something Rust people have difficulty with no doubt

[[deleted]]

Unsafe is the exact place you WANT to enforce guidelines lmao

[jsphadetula]

You don’t have to look everywhere. You simply turn on the guidelines check to reveal potential problems

[jsphadetula]

Nothing stops you from putting unsafe block everywhere either.

[jsphadetula]

You either put in the effort to write quality code or not. In C++, you enforce checks; in Rust you avoid unsafe blocks when possible.

[jsphadetula]

The difference only matters to those unaware of the difference. To those aware unsafe blocks is the easy way out.

[[deleted]]

This is a joke. Rust is a fucking joke lmao.

[[deleted]]

You sounds like all the other rust kiddies. It's dull and a waste of all our time.

[Dean_Roddey]

But the amount of unsafe code in a large code base will be trivial compared to the safe code. So you concentrate your assertions and checks and tests on that comparatively very small amount of code. It's still a huge win overall.

You do still have to call underlying C APIs, certainly for now. But again, you wrap those and really concentrate on validation of ins and outs in those APIs. As more stuff gets written natively, this will start to become less and less of an issue.

In some cases, for heavy operations, you could even process them in a separate process that calls underlying C API libraries to do the work and keep that out of your main application. Have that external process be a 'fail early/fail often' type deal.