I'm not really a C++ coder, but it seems the industry could really use some sane standardized C++ subsets that allow stuff like this without so much fricking complexity
Rust is allegedly liked because it brings the safety without the overhead (performance wise)
c++ variants suck ass because its tacked on not baked into the language like in rust. The rust standard library is designed around it so it feels well to use it. C++ need a different approach to have it fit in.
>implies Rust's shit is zero cost.
lmao, I looked at a disassembly of a relatively simple native plugin and was shocked at how much shit rust performs just to do what is effectively a couple of if else statements with few instructions. Yes man we gotta check for overflow on every little operation you do, yes man calling 10 functions before you do a simple deref/call/borrow is essential for you, yes you are hecking cute and valid and wont krill yourself when you are bit over 30.
Nothing should cost the user's time, but because nobody in Rust community is keen on shipping real things which are not worse rewrites, developer ergonomics are above all else.
Always hilarious reading about using "modern C++". While every serious project is written in the C+classes style.
Not that "modern C++" is any good, or a real coherent thing, or even a fixed construct.
Actually, ceepeepee tards COPING by hinging on a rolling construct is the best part.
you avoid most of those issues in C++ if you just use modern language features, dont even need to do anything special
Rust is a joke, if I want "guaranteed memory safety" I would use C# or Java, they bring as much overhead as Rust does
I'm not really a C++ coder, but it seems the industry could really use some sane standardized C++ subsets that allow stuff like this without so much fricking complexity
Rust is allegedly liked because it brings the safety without the overhead (performance wise)
Rustroons on suicide watch
Rust still has the better community :3
that's not better, that's much worse actually
that's what I look for in my tools. the community.
t. proud screwdriver community member
Wait...are screwdriver users angry trannies too?
Most cniles are trannies.
Nice try troon, C is widely known as the language of choice for the discerning white power supporting Chud
reported for logo copyright infringement
it's in the rust press kit
>fsanitize=thread
What even is that just use a mutex/atomics homie
I never used any of these in C++, my code just works by default
C++
std::variant<Fluid, LightItem, HeavyItem, FragileItem> package;
std::visit(overload{
[](Fluid& ) { std::cout << "fluidn"; },
[](LightItem& ) { std::cout << "light itemn"; },
[](HeavyItem& ) { std::cout << "heavy itemn"; },
[](FragileItem& ) { std::cout << "fragilen"; }
}, package);
Rust
enum Package { Fluid, LightItem, HeavyItem, FragileItem };
match package {
Fluid => println!("fluid"),
LightItem => println!("light item"),
HeavyItem => println!("heavy item"),
FragileItem => println!("fragile"),
};
Yeah, I'll stick with rust
Pattern matching scares the Chud++ dev
we can already see patterns so we don't need language implementation to find it for us
>Comparing type matching to enums matching
Not only are these not equivalent, they have nothing to do with each other.
Please do stick with rust, you'll fit right into the crowd of trooned out tards.
this looks terrible
>t. javascript/typescript dev
c++ variants suck ass because its tacked on not baked into the language like in rust. The rust standard library is designed around it so it feels well to use it. C++ need a different approach to have it fit in.
rust always looks good when I see it in small snippets then you look at a large code base and it’s all dogshit
git gud nocoder
Sanitizer is good, but it's not zero-cost.
>debug-only thing is not zero cost
>implies Rust's shit is zero cost.
lmao, I looked at a disassembly of a relatively simple native plugin and was shocked at how much shit rust performs just to do what is effectively a couple of if else statements with few instructions. Yes man we gotta check for overflow on every little operation you do, yes man calling 10 functions before you do a simple deref/call/borrow is essential for you, yes you are hecking cute and valid and wont krill yourself when you are bit over 30.
Nothing should cost the user's time, but because nobody in Rust community is keen on shipping real things which are not worse rewrites, developer ergonomics are above all else.
>Yes man we gotta check for overflow on every little operation you do
Release builds don't check overflow.
You were looking at a debug build...
Always hilarious reading about using "modern C++". While every serious project is written in the C+classes style.
Not that "modern C++" is any good, or a real coherent thing, or even a fixed construct.
Actually, ceepeepee tards COPING by hinging on a rolling construct is the best part.
https://loglog.games/blog/leaving-rust-gamedev/