This btfos Rust trannies

>unemployable cnile spreads lies
Who knew. `char` in Rust is a unicode character, not an ASCII character. Here's a fair comparison, and would you look at that. Used the same compilers as you as well since GCC actually doesn't optimize it as well, it's almost like Rust and clang have the same backend!

Attached: lol.png (1920x969, 89K)

Actually it works with char too, nevermind. This guy here is right What the fuck are you doing OP

>you need to learn this strange unreasonable construct to make rustc produce equivalent machine code
this is why rust will never replace anything. dilate

In his defense he could actually be a cnile, at least he's using C++.

Cope harder and RTFM you fucking low IQ cuck

Attached: Screenshot from 2019-08-04 01-31-58.png (3782x1838, 302K)

>matching is "unreasonable and strange" construct
Ah yes typical cnile

Attached: 1537771566378.png (1200x1400, 502K)

>this strange unreasonable construct
the cope levels are through the roof!

Attached: 1564273287308.png (540x770, 325K)

I love the smell of OP being BTFO in a morning.

Attached: 1542024671555.png (231x330, 70K)

Chances of trannies an heroing: 40%
Chances of OP an heroing: 100%

Attached: 1551246726668.png (1799x825, 263K)

>match
>strange
>unreasonable

Attached: 1549755834302.jpg (425x283, 18K)

I actually get it now! The difference between the C and Rust code here is that Rust actually ensures that a||b is checked a then b (C or C++ doesn't), while a match expression is just "any of these", that's why the match works, it's not "making rustc produce equivalent machine code".

Attached: eDRFAPV.png (434x434, 195K)

Cniles B T F O

Attached: segfaulting cnile.png (627x722, 114K)

kek

Yes, Rust produces predictable binary here.
Based Rust.

>t flutter cuck

>even switch is optimized but a simple, readable compound condition is not
there is no need to reinvent the wheel if you won't add better features, and that stupid match thingy isn't one

the fact the complier doesn't optimize it to that automatically is fuckin dumb though

to be fair unicode handling is usually how ctards cheat on benchmarks

>What the fuck are you doing OP
Coping

Yeah, except rustc here recognizes that the cases are all ASCII characters and treats the comparison as such.

live steam your suicide, coping retard haha

See: It's different code.

>pattern matching doesn't add better features
How shaky were you when writing this deluded post?

Attached: knifedasusual.jpg (250x250, 40K)

>you won't add better features
this

Attached: 1554750438282.gif (640x358, 1.94M)

>no argument, just trying to tease with "haha"
typical tranny

Guys, go easy on OP. Maybe he'll spend more time learning instead of shitposting.

God I don't miss my CS101 days, gg OP.
You either are extremely fucking retarded or baiting for attention. Or even false flagging cniles.

Cniles are already a laughing stock now, no need to false flag them.

Nah, he's spouting "muh tranny", he had no intention of learning anyway and needs to go back to his containment board.

HAHAHAHA GET FUCKED OP

Attached: 1535481011618.jpg (805x604, 132K)

>pattern matching a fucking single character
omg I love rust now

Probably his defense mechanism after spending too much time on 4chin. He's just shook after getting BTFO.

I mean, yeah, a | b | c | d still looks better than thing == a || thing == b || thing == c || thing == d

samefag
get the fuck out of my board tranny

Pattern matching != regex matching

You colossal coping retard

Nevermind, OP sucks cocks.

>looks better
arguable. a single pipe is for bitwise OR, double pipe is for conditional OR. a | b | c | d may look like an uncut bbc to your tranny eyes but it doesn't make sense

u ok OP? U there? Opie ?

The cope just never ends!
>get the fuck out of my board
No, you head the fuck back to your containment board before you get BTFO this hard again.

Attached: 1562649620368.gif (500x357, 358K)

>a single pipe is for bitwise OR, double pipe is for conditional OR
Same in Rust you seething mincing coping showerless kissless incel

Why would anyone use regex to match a single, primitive character? I don't follow you, did you take your estrogen pills?

then why are there single pipes in that match thing dumbass?

ITT OP shitposts to have Jow Forums teach him rust

Nobody told you to use regex to match a char, did you even read the post or did IQ dropped sub room-temperature level suddenly after getting BTFO?

>seething mincing coping showerless kissless incel
she doesn't even know how to insult effectively. absolute state of rustfags

Operator re-use. Every language, including C has it.

none, I'm telling you I don't follow, take your pills, suck some dick and get some sleep

char* c;
*c // wait why is there a pointer sign next to c what the fuck

>I'm telling you I don't follow
That's just because you have a very low IQ and hence the lack of reading comprehension.

This pleb has never written OCaml? Disgusting.

It's pretty unintuitive that rust even considers the 2 cases different.

no, it's not, predicates can take any arbitrary boolean expressions

the fucking C bashing threads are really discouraging my learning. Please stop guys.

I want cniles _dead_. Not just discouraged or discrete. I want them fucking dead. and I won't stop until they all kill themselves

>29 IPs
>60 replies

You can't assume it's all ASCII because you don't know which character will be at input.

OP fucking BTFO

>optimized
the order matters for short-circuiting

no, he's a trannydilatecuck poster

that's a multiplication sign idiot

yeah, that too lol

The level of cope in this thread is unreal

Attached: E81D4462-96AB-4D51-A673-5AE9CE242BAE.png (156x150, 51K)

But can you still not implement a doubly linked list in safe rust?

You can, as I'm sure you remember from getting absolutely blown the fuck out last time you brought it up. Do you actually know what a doubly linked list is this time?

oh it's THIS retard again. You always could
struct Node {
data: int,
previous: &Node,
next: &Node
}

sorry, i32 or whatever other datatype you want

Show compilable code for splicing a new element into the list in O(1) time.

>splicing a new element into the list
>O(1) time
Oh, so you still don't know what a linked list is.

>already moving the goalposts

A simple doubly linked list inserts in O(n) time in C++, as in Rust

struct Node {
int data,
Node *prev,
Node *next
}

Samefag. Too many samefags itt.
77r,34p

Literally the entire point of doubly linked lists.
This is stuff you learn in introduction data structures and algorithms.
Only if you need to find the node first. Insertion or splicing if you already have a pointer to the node in question is O(1).

>if you already have a pointer to the nice in question
This is exactly why insertion is O(n)

>only if you need to find the node first
it's assumed that you do when you're talking about insertion time you fucking brainlet

dude, you made the same bullshit argument last time and got soundly blown out. you're embarrassing yourself

https : / / bit dot ly / 2LYqUsG
No unsafe necessary whatsoever.
Fuck Jow Forums's spam filter.

If you have a reference to the node then yeah, it's easy. See the Node::append() method in the playground gist above.

Plenty of cases where what a node represents keeps a link to it for cases like this. But let’s pretend that isn’t the case. Show compilable code where you can even splice a list into the middle of a doubly linked list.

again, you're arbitrarily moving the goalposts (and seem to miss the point of big O notation) but here you go:

This is nice. Shame it needs reference counting but does seem to work.

i want to be cool like the rust users but im dumb and can barely understand go tutorials

damn, generics in rust are clean as fuck

rekt

I am just asking for friend! I am not interested in tranny rust!

let f = Rc::new(RefCell::new(Node::new(data)));
self.first = Some(f.clone());

why is clone necessary if f dies anyway?

>phpcase
fuck off back to Jow Forumsprogrammerhumor

Doesn't matter.

Rust is filled with more bugs than the game

Oh no op are u ok?

do you guys don't realize how disgusting your language looks?
it has like double of symbols for no reason and probably is driving the parser fucking crazy.

also on a side note, so basically i could write "safe" Rust code and then using LLVM translate it to C? making programing languages even more useless?

>Cniles
everyone sees though this shit dude we aint childrens.

en.wikipedia.org/wiki/Imprinting_(psychology)#Baby_duck_syndrome

>2022
>still has to put C bindings because if not no one is going to use their language.
absolute state of faggots.

>we aint childrens.
Yea... he's literally calling you the opposite lel

and the point is that we should all learn Chinese because it has more symbols?/
Get the fuck out with your imprinting theorems