Dozens Of Rust Updates Merged Ahead Of GCC 13.1

[jasonjulius1122]

Hi! hope you all are well, I have heard some exciting news! GCC 13.1 is close to release, bringing enhanced Rust language support with merged "occurs" patches. Rust developers using GCC can look forward to improved capabilities and compatibility. Stay tuned for the upcoming release!

[lowflyer]

... Lowflyer, to whom I won't talk anymore in this thread, ...

An invitation to start bashing rust without nuisance from a certain obnoxious brat ?

Naah.

As I already said: rust is "just another language". And a fine specimen so far. It can very well stand on its own merits. It doesn't need my help. Unfortunately I cannot say the same about its rustafarians. They do more damage than good. And they're not wise enough to see it.

[oleid]

Sounds like a troll move.

That follow request was actually an accident on my end. Sadly, there is no way to undo such a request in this forum.

[coder]

You are absolutely correct. I guess you had exchanges with oleid that I didn't follow.

No, I meant jacob. I don't usually engage in these Rust discussions, but there was another thread where he baited me into a pitched battle that he really just seized upon as an opportunity to spread more FUD about C++.

As for oleid , I only followed some of your exchange here.

oleid sent me a follow request. Which is quite surprising after this exchange. I'll ignore it, as I do not follow his religion.

Sounds like a troll move.

[oleid]

It's worse than that. He will seize any and every opportunity to exaggerate, misrepresent, and generally shit on C++ that he possibly can.

Please tell me where I shat on C++ in this thread.

By the way, I'm using C++ now for over 9 years professionally at my current employer (hobby usage is much longer, I started with c++ before even c++98 was standardized). So I don't see why I cannot criticize it, since I know it's flaws and strengths.

Lowflyer, to whom I won't talk anymore in this thread, confirmed that his intellect is doing honors to his nickname. He took every means possible to misinterpreted what I wrote and derail this thread.

[lowflyer]

It's worse than that. He will seize any and every opportunity to exaggerate, misrepresent, and generally shit on C++ that he possibly can.

...

You are absolutely correct. I guess you had exchanges with oleid that I didn't follow. I certainly like to whack the bushes until the monkeys come out.

oleid sent me a follow request. Which is quite surprising after this exchange. I'll ignore it, as I do not follow his religion.

[coder]

I'm not arguing. I understand you are sold out to rust and its philosophy. I understand that you're not willing to hear that C++ can be had easier.

It's worse than that. He will seize any and every opportunity to exaggerate, misrepresent, and generally shit on C++ that he possibly can.

Some people will do unscrupulous things, when they feel their cause is righteous. He is a holy warrior of the Rust Cargo Cult. The only way to deal with these trolls is to call them out, but don't try to engage on the facts. The resulting exchange will never be completely above board. All it does is give him more opportunities to spread anti-C++ propaganda.

[lowflyer]

Anyway, I see discussing with you is pointless. Have a nice life.

As quick as the monkeys came out of the bushes, they disappeared.

Earlier I said this:

I understand that you're not willing to hear that C++ can be had easier.

+1 for me.

[lowflyer]

...

It took me quite some posts to chase the monkeys out of the bushes...

Compare apples with apples! You didn't shy away from pasting the full plethora of clang diagnostics and compare it with rust that stops after the first error. A similar behavior from clang can be had with specifying `-Wfatal-errors`. As a senior programmer that advises juniors, I would expect you to know this. Together with the advice "check the first error message first".

You bemoan exclusively the length of the output and not the content:

invalid operands to binary expression {'std::vector<int>' and 'const int'}

can't compare `{integer}` with `Vec<i32>`

no match for 'operator==' (operand types are 'std::vector<int>' and 'const int')

I leave it up to you to decide which of the messages is more useful. GCC prints less lines than rust.

[oleid]

To compare apples with apples: Create a dangling reference in a unsafe code section and let the build system and a gitlab CI cope with it.

Well, no. Unsafe is forbidden by default. So it's apples to apples.

Anyway, waiting for your setup.

I'm pretty sure that something akin to dangling references - or even something much worse - will be introduced to rust at some point.

I knew you would say that. Typical forum troll strategy.

Anyway, I see discussing with you is pointless. Have a nice life.