[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology

Name
Options
Comment
Verification
4chan Pass users can bypass this verification. [Learn More] [Login]
File
  • Please read the Rules and FAQ before posting.
  • You may highlight syntax and preserve whitespace by using [code] tags.

08/21/20New boards added: /vrpg/, /vmg/, /vst/ and /vm/
05/04/17New trial board added: /bant/ - International/Random
10/04/16New board for 4chan Pass users: /vip/ - Very Important Posts
[Hide] [Show All]


[Advertise on 4chan]


File: maxresdefault-30.jpg (139 KB, 1280x720)
139 KB
139 KB JPG
After using Rust, C++ now gives me the ick.
>>
>>106435392
This is such a toy example there's barely any difference.
>>
>>106435392
This example makes C++ look good.
>>106435446
Well, slightly better.
>>
>>106435392
>gives me the ick.
Only little bitches talk like that.
>>
>>106435392
>#[derive(Copy, Clone, Debug]
lol
>>
So trait is like interface?
>>
>>106435803
yes problem? They let you print a struct and allow you to pass by value without using the .clone() method.
>>
>>106435392
>indentation of 2 spaces
>declaring functions with auto
good morning saar
>>
>>106435392
>fn go_fuck(my_self) -> pedantic_integer32_imgay
>#[derive(Clone, Copy, Debug)]
What?
>>
>>106435392
Why do you only use languages that are unintuitive clusterfucks. Are you german maybe? Do you like SAP?
>>
File: GxL0QroXoAAEetU.png (55 KB, 862x386)
55 KB
55 KB PNG
>>106435392
this is why I went back to C, neither of these two languages have any killer feature, C is good enough.
>>
File: me.png (74 KB, 251x284)
74 KB
74 KB PNG
>>106438104
Templates? Namespaces?
>>
>>106435392
You probably couldn't pick worse code for comparison. It's literally the same just different syntax.

>>106436654
Not quite. Interfaces generally mean duck typing and just say that specific type provides specific set of functions/members. They are part of class declaration.
Traits on the other hand have to be implemented onto some type. It can even be primitive or a tuple or they can have blanket implementations that cover many or all types using some generic bounds. They are more general and can also be used to extend functionality of primitive and external types.
>>
>>106437173
>filtered by types
Cniles are pytoddlers in disguise
>>
>>106439023
That's not a very good explanation of rust traits imo. Rust traits are not interfaces or traits, they're type classes. To be a trait mixins must be supported and rust doesn't have that. To be an interface it would need subtyping. Rust actually has adhoc polymorphism, so it's not an interface or a trait. They probably called trait to avoid confusion with OOP terms.
>>
By using Rust you agree to the statement that trans women are women.
>>
>>106439023
It looks a bit like extension in Beef
// interface
interface Shape
{
public float Area();
public float Perimeter();
public float AreaPerPerimeter() => Area() / Perimeter();
}

// type declaration
struct Cirlcle : this(float radius);
struct Rectangle : this(float width, float height);

//extending Circle by implementing the Shape interface
extension Cirlcle : Shape
{
public float Area() => radius * Math.PI_f * Math.PI_f;
public float Perimeter() => radius * 2 * Math.PI_f;
}
// doing the same with Rectangle
extension Rectangle : Shape
{
public float Area() => width * height;
public float Perimeter() => (width * height) * 2;
}

public static
{
// extending every type that implemented Shape
public static void Print<T>(this T shape) where T : Shape
{
Console.WriteLine("Area per perimeter of {} = {}", shape.GetType(), shape.AreaPerPerimeter());
}

// add a Square method to any types with the * operator
public static T Square<T>(this T n) where T : operator T * T
{
return n * n;
}
}
>>
>>106439023
A lot of wrong information in your post, sorry.
>>
>>106435392
C++ is one of the ugliest and most retarded languages (I'm talking about the way you have to do classes in it), so yes, Rust wins here. I had to write C++ during school and I would have rather written Rust. I don't know Rust, thoughbeit.
>>
>>106439023
Aren't the syntax and safety features the main draw of Rust? Rust is supposed to be C++ but safe and sane, or something.
>>
>>106439663
The type system, ML-ness, and dev experience (tools, compiler warnings)
>>
>>106439347
Types in almost all languages: you define the things you can do with an object

Types in C++ and Rust: you define all the things you cannot do with an object

C++ has the excuse that a ton of code is written in it, so the language, as bad as it is, has a reason to exist.
Rust is an abomination that will fortunately be forgotten in a decade. No one is written anything serious in Rust, because as soon as the project grow beyond a certain size, you gridlock yourself to death with the retarded type system.
>>
>>106439663
The safety features are the cherry on top, not why i use rust.
>>
>>106439801
If type masturbation is your thing then you'll love Haskell.
>>
>>106439785
>Types in C++ and Rust: you define all the things you cannot do with an object
This is so wrong about C++, it's funny
>>
>>106436659
Looks incredibly gay. Like "look im unique, pay attention to me" level gay. At least in c++ everything is straightforward if you pay attention.
>>
>>106439815
No Java takes the cake on stroking your keyboard for reaching a goal
>>
>Rust is just better, designed sanely
The Rust borrow checker could be a whole thread of discussion.
Orphan types.
Pinning.
Rust is not yet fully specified, it is an active area of research.
Type system holes.
Solver woes (like, what even are these issues https://github.com/lcnr/solver-woes/issues ).
Unsafe being significantly more difficult than C++.
Panics not being exceptions, except sort of when a crate/project setting is used to not abort upon panics, but make the program unwind upon panics, and then in some cases letting catch_unwind catch the panics (the panics that are not exceptions, remind you), and unwind safety being something that Rust developers have to know about when using that setting AFAIK, similar to C++ exception safety.
>>
File: 1731737408129300.jpg (101 KB, 1634x1256)
101 KB
101 KB JPG
>>106435392
apparently, rust is named after a type of fungus that causes rust-like scabs to appear on a person's skin.
the fungus is known to be very resilient in harsh conditions, which i guess kinda sorta makes sense in the context of their scripting language. nonetheless i wish they chose something more pleasant.
>>
>>106440818
Forgot to mention the time crate 1.80 debacle.
https://internals.rust-lang.org/t/type-inference-breakage-in-1-80-has-not-been-handled-well/21374
And the multiple different crates that the Rust community have authored for avoiding the borrow checker due to it often being unergonomic. https://donsz.nl/blog/arenas/
https://www.reddit.com/r/rust/comments/1etbfym/a_comparison_of_every_arena_in_rust/
>>
File: 1756592012415030.jpg (52 KB, 640x622)
52 KB
52 KB JPG
>>106440818
This is propaganda, rust uses panics for unrecoverable error states, C++ throws invisible exceptions for simple shit like parsing integers with std::stoi

Also the rest of the post is extremely disingenuous for trying to portray C++ type system better. SFINAE is the only example I need to show how broken C++ is. There is an entire web page pointing out the defects of C++
https://yosefk.com/c++fqa/defective.html
>>
>>106439023
>It's literally the same just different syntax.
It's not the same at all niggers.

>>106435392
Whoever made this pick is a faggot. The C++ equivalent would have been with concepts, not fucking boomercore inheritance.
>>
>>106439446
Can you remind me what programming has to do with social or political issues?
>>
>>106435392
Okay, but Java is the only language worth knowing
>>
>>106441156
Not if you want to do hardware or OS related software.
>>
>>106439446
>>106441143
Monologue.
>>
>>106435392
circle inheriting from circledata? virtual inheritance? your problem is that you are just bad at programming.
>>
>>106441019
>This is propaganda, rust uses panics for unrecoverable error states, C++ throws invisible exceptions for simple shit like parsing integers with std::stoi
Laughing out loud. Nothing I wrote was wrong.
https://doc.rust-lang.org/std/panic/fn.catch_unwind.html
https://github.com/actix/actix-web/issues/1501#issuecomment-626721902
>On catch_unwind, trying to employ a system that relies on catch_unwind has all sorts of gotchas including considerations of things that are or are not unwind-safe; it is not equivalent to try-catch in other languages that are built to handle clean up.
https://users.rust-lang.org/t/stop-terminating-rust-actix-web-application-on-error/99502/2
>That is not the normal behavior. Tokio (which actix-web uses) will catch panics in tasks, which prevents them from bringing down the process.
>Perhaps you could say more about what kind of error is happening? Maybe you have a double panic, where the thread panics during a panic. This is pretty rare, but will bring down the process.

>Also the rest of the post is extremely disingenuous for trying to portray C++ type system better. SFINAE is the only example I need to show how broken C++ is. There is an entire web page pointing out the defects of C++
Yet C++'s type system appears to be simpler than that of Rust. That is not a good accomplishment by Rust.
>>
>>106441019
>std::stoi
std::from_chars is the one you want in C++ since it's not retarded as fuck. I don't want to defend C++ but you can either use the better functions, or you can catch the exceptions when parsing. The manual memory management argument in your link is a retarded "defect," since it is absolutely necessary in embedded. Feel free to use the Boehm GC if you don't want to do manual memory management in C or C++.
>>
>>106435392
you forgot implement over 9000 constructors in c++
>>
>>106439590
Can you do a blanked implementation like
impl<T> Shape for T where T: Curve + Closed { ...

Which would implement trait/interface onto every type that has Curve and Closed traits?
>>
File: 1746489692652.jpg (199 KB, 756x528)
199 KB
199 KB JPG
>>106441019
>https://yosefk.com/c++fqa/defective.html
>revised 17 October 2009
>>
Why is the concurrency fearless?
>>
>>106440818
And what exactly is bad about these things?

>Panics not being exceptions, except sort of when a crate/project setting is used to not abort upon panics, but make the program unwind upon panics, and then in some cases letting catch_unwind catch the panics (the panics that are not exceptions, remind you), and unwind safety being something that Rust developers have to know about when using that setting AFAIK, similar to C++ exception safety.
They do different things. C++ exceptions are generally meant to be caught and handled.
In rust you only catch panics to display some message or whatever and then you should continue to close the program. They are not meant to be handled.
>>
>>106441301
>Yet C++'s type system appears to be simpler than that of Rust. That is not a good accomplishment by Rust.
Value categories, incomplete types, 5 kinda of constructors, SFINAE, templates fuckery, etc. No, C++ type system isn't simpler. It might be less abstract, but it's so bloated it's incomparable.
>>
>>106441457
Send+Sync are used to prevent data races. Every type is known if it can be safety moved or shared across threads.
>>
>>106435392
>after getting a piss fetish, shit fetishes give me the ick
>>
>>106441301
>Nothing I wrote was wrong.
No but your implication was. Rust uses Result type for error paths and panics only for unrecoverable error states.
C++ uses hidden exceptions at all times.
>actix
Not standard library. I can bring up inane bullshit on Qt as well. Quit your propaganda.
>>
File: 1751780442947603.jpg (78 KB, 885x498)
78 KB
78 KB JPG
>>106441453
And?
>>
>>106435392
>auto type returning function
hazardous
>>
>>106441600
auto is not the return type here, it's the C++11 trailing return type
https://en.wikipedia.org/wiki/Trailing_return_type
Back in 2011, Bjarne Startup realized the C style denotation of function return type was a stupid idea.
Inside C++ there is a much cleaner and saner language that wants to see the day of light. And that language is called Rust.
>>
>>106441461
Low-IQ, retarded, incompetent troll, rope yourself.
>>
>>106441471
>Value categories
Rust has that as well, incompetent, inept, negative-worth troll.
https://doc.rust-lang.org/reference/expressions.html#place-expressions-and-value-expressions
Rope yourself.
>>
>>106441582
>>106441590
>>106441616
I didn't imply anything. And the Rust language development issues explicitly describes and mentions that use case and justifies it.
Retarded, idiotic, moronic troll, off yourself.
>>
>>106441616
oh i see. ngl modern cpp is too uncanny for me
>>
>>106441350
>or you can catch the exceptions when parsing.
That wasn't the point. The point is in C++, exceptions are meant to be handled, in Rust, panic is rarely meant to be handled.
C++ expresses recoverable error path using hidden exceptions and that's a problem.
>>
>>106441656
Value category is not value expression, Rust does not have it. Meaning none of lvalue, rvalue, xvalue, prvalue, glvalue are Rust concepts. You tried to cherry pick one of the C++ defects he mentioned and failed to defend it.
I understand you are not a programmer and almost 100% of your programming knowledge comes from random google searches but you should at least do your research before making a fool of yourself.
>>
>>106441703
>C++ expresses recoverable error path using hidden exceptions and that's a problem.
It's a different trade-off. I personally prefer error types, and Rust has better support for those than C++, but there are definitely trade-offs, also for users. And Rust even has issues in their support for error types in some cases, OCaml has significantly better support in some of those cases than Rust AFAIK. Consider the popularity of the "anyhow" crate, which undermines some of the advantages of error types, but which is used to help mitigate those issues in Rust.
And panics are still in some types of Rust applications caught, like maybe the very popular Actix and Tokio. Even though the norm definitely is error types. And it depends on crate/project settings whether panics abort or unwind, which does not seem clean to me.
>>
>>106441747
Personally, I come from F# background and do notation would be really nice.
Some of the design choices to propagate errors were too verbose, Rust needs to fix that for sure.
>>
>>106441743
You incompetent, lying, negative-worth buffoon, rope yourself.
https://doc.rust-lang.org/reference/expressions.html#r-expr.place-value.place-context
>Historically, place expressions were called lvalues and value expressions were called rvalues.

C++ "value categories" could possibly have been named "expression categories".
>>
>>106441768
lmao sure, Rust is an expression based language, everything is an rvalue. If you are that desperate to draw parallels with C++ value categories then show me xvalue, prvalue and glvalue you autistic nigger.
>>
>>106435803
derive ~ dilate
>>
>>106438228
C does not need any of this shit especially template.
I don't understand what's the deal with zoomers and their obsession with generics, why do you care SO much about them?
they were never needed to write anything good, they're never implemented correctly either, there is not a single good reason to add them to C
>>
>>106441792
Demented, deceitful troll, are you using a chatbot to create your messages for you? Off yourself.
>>
>>106441143
Everything when its entire creation team and all its users are more concerned with their festering axe wound politics than anything else.
>>
>>106441747
>Consider the popularity of the "anyhow" crate, which undermines some of the advantages of error types, but which is used to help mitigate those issues in Rust.
How does it undermines it? It's just convenience library for programs where you don't need strongy typed errors. You don't use it for libraries and that's where precise error types matter. In your program, when you are interfacing with a library, you can still get all the benefits of exact error types to match and handle them, and then you can discard that information when you throw it deeper into your code logic to make it much easier to mix various error types from various places. You literally get best of two worlds.
>>
>>106441881
Don't be mad at me, blame your lack of knowledge. Concession accepted.
I'm gonna let you have the last word out of pity because that's how your algorithm thinks you "win" an argument. No judgement :)
>>
>>106441881
>no argument
As expected
>>
>>106441372
Underrated lmao
>>
You literally posted some dumb example from like Programming Principles with C++. Opinion discarded
>>
>>106435392
The only reason I still choose C++ over Rust is that C code is valid C++.
>>
>>106438228
Namespaces is a feature that I like in C++ but I don't find them necessary in C because I just use a renaming macro in C when there's a naming conflict.
>>
>>106441441
I don't think so, no.
>>
>>106441914
>>106441915
>posting times
Demented, lying, inept, low-IQ troll, off yourself.
>>
>>106441919
>>106442132
>>
Why does the rust crap look exactly like C but more mind bending?

>Here is NEW THING
>It's like OLD THING, but the compiler takes 8 gb of ram to compile itself, so no compiling on old computers!
>Also we don't have to talk about Richard Matthew Stallman anymore:
>Did you know RMS dissed a Woman and hated them in the 80s?
>He also wants to fuck and dominate cute little girls.
>Men should have their dicks sawn off like Jesus says (matthew 19 greek!) , anyone that looks at a woman should have their eyes gouged out! Don't stone woman
>RMS is a JEW and won't agree to Jesus' demands.
>>
>>106441792
that's racist
>>
>>106442072
it's not. and your factually wrong talking point is 26 years out-of-date. not that a larping /g/eet tard like yourself would know.
>>
>>106441768
The Rust evangelist was too incompetent to understand his own language.
>>
Both are deprecated in the current year
You Only Need Java
YONJ
>>
>>106435392
Return type on the end is utterly disgusting. Why would you do this unless its needed (templates)
>>
>>106444278
Let's see how would you write a type of a function that takes a function and returns a function.
>>
i really dont wanna go into inner workings of Rust and if its perhaps superior and more performant language
but that syntax... holy fuck like why, how was it allowed too look that ugly and unreadable in this day and age?

insane
>>
File: 1755620507978.png (248 KB, 480x640)
248 KB
248 KB PNG
speaking of
what happened to all the Golang shills?
I wrote a scraper with it and thought subroutines were great
>>
>>106444569
What would you change in Rust syntax to improve it without losing any of expressiveness or safety?
>>
>>106435392
Man, all this shit is so niggerlicious... God bless C.
>>
>>106444724
NTA, but some of Rust's syntax is the way it is due to backwards compatibility and historical baggage. A minor example is probably the symbol to indicate return type of a function, which would IIRC have been ":" instead of "->" if not for some issue or another.
>>
>>106440778
>anon encounters something somewhat unfamiliar
>immediately starts crying and thinking about being gay
repressed homo
>>
>>106444278
vertical alignment
>>
>>106444948
fn(fn() -> Ret) -> fn() -> Ret is more readable than fn(fn(): Ret): fn(): Ret
>>
>>106435803
c++ is copying this badly.
>>
>>106444948
Rust arrow was intentional to be more readable. They wanted to avoid confusion with argument types and return types. It was copied from C++11 trailing return.

I find it silly because there's no real difference between a argument type and a function return type, but that's why. Now it's not generic enough, but I could say the same of any programming language without currying.
>>
>>106437050
>indentation of 2 spaces
>declaring functions with auto
https://clang.llvm.org/extra/clang-tidy/checks/modernize/use-trailing-return-type.html
Those are purely stylistic choices that have nothing to do with the quality of the code
>>
File: dalek.jpg (244 KB, 2000x1000)
244 KB
244 KB JPG
IDENTIFICATION DIVISION.
PROGRAM-ID. EXTERMINATE.
ENVIRONMENT DIVISION.
PROCEDURE DIVISION.
DISPLAY 'EXTERMINATE! EXTERMINATE!'.
>>
>>106442936
Why are you talking to yourself?
>>
>>106435392
Rust is less ugly but I think I'd still rather use C
>>
>>106444765
I thought Niggerlicious was used to describe code that is complete voodoo hoodoo nonsense that you can't reliably read and figure out just off of reading it alone. Both code snippers I can reliably figure out the majority of it without knowing either syntax since my programming knowledge is C (Nearly divine), Python (Supremely Niggerlicious) and Java (niggerlicious)
>>
>>106441863
>I don't understand what's the deal with zoomers and their obsession with generics
people were using generics long before first zoomer was even born.
>they were never needed to write anything good
C was never needed to write anything good
>they're never implemented correctly
elaborate
>there is not a single good reason to add them to C
agreed
>>
C++ bros... our response?
>>
>>106445499
Java does not need this so why does C++ need it
>>
>>106446510
>i love using languages with no generics or collections in the standard library
reddit is that way
>>
>>106444765
>>106446510
You should kill yourselves you useless midwits
>>
>>106445398
>I find it silly because there's no real difference between a argument type and a function return type
What? There is no real difference between an existing computed value and a value you don't have, so you know nothing about it except it's type and which can't get without running a computation and possibly creating and/or passing a bunch of other values? Values which given computation can outright consume with no way for you to get them back?
>>
god I hate the concept of virtual functions
>>
>>106447303
>people were using generics long before first zoomer was even born.
yeah but boomers aren't spamming "but no hashmap xaxaxaxaxa"
>C was never needed to write anything good
>hurr actuality you can zipzap electricity yourself, you don't need to code
yeah no shit but take your autismo pills, no one has any fuck to give about your pedantic/absolute relativism non-sense
>elaborate
there are many ways to implement generics, ask your favorite AI to tl;dr monomorphism, erasure or reification for you (or take your old CS courses, if your uni wasn't dogshit you saw this shit already).
languages make tradeoffs, C++ generics are using monomorphism or parametric polymorphism ie compile-time polymorphism, that put many limitations on what you can do with these things at runtime and can bloat binaries, I can't think of an example right now but the usual limitation of templates are usually because of the implementation.
also the theory is usually much more complex that what we get in language from the top of my head : no higher-kindred types like in haskell and quite lax rules around template instantiation see SFINAE.
>>
>>106448913
If C is so great because muh simplicity then go program in Assembly, faggot.
>>
>>106448979
no thank you, C is the right abstraction for most things.
>>
Sorry kid but HolyC is the future kid
```
U8 *str="King Terry A. David";
"%s\n",str;
```
>>
Rust is an antiandrogen
>>
>>106435392
Is it AI shit translation, or why are you forcing everything on struct.
This could be done cleaner with fairly basic c++
>>
>>106449527
Nice post, redditor. Still no fitting in
>>
>>106445062
>>106445398

Your arguments are strange.

Comparison with Rust, Scala and OCaml:

Rust:

fn a() -> fn(i32) -> fn(i32) -> i32 {
panic!();
}

fn b() -> fn(i32) -> dyn FnMut(i32) -> i32 {
panic!();
}


Scala:

def a(): Int => Int => Int = {
throw new Exception()
}


OCaml:

let a (): int -> int -> int = raise (Failure "test");;


In Scala and OCaml, it is easy to differentiate between the function declaration or definition, and the return type.

In Rust, I don't even know what to say. It's uglier than I anticipated.
>>
>>106446225
Do you acknowledge that it/you are too incompetent to understand its/your own language, as >>106441768 shows?
>>
>>106441441
you can, but it has gotchas.
In C++ that would be easy using concepts, however rust doesn't perform specialization-based resolution for generic overloads.

that means that once you have:
impl<T> Shape for T where T: Curve + Closed { ... }

// Then if you have
struct CustomShape { ... }

impl Curve for CustomShape { ... }
impl Closed for CustomShape { ... }

// Then you can't do this:
impl Shape for CustomShape { ... }
// This will fails to compile, due to the more generic version above. You could use negative traits to get around this, but they're not fully implemented as of yet
>>
>>106441457
it's not, rust still has race-conditions. and there are perfect concurrency patterns, like spmd, that aren't covered by send+sync.
that said, send+sync is really helpful as it'll catch rookie mistakes, like forgetting to put a mutex on a variable, but it can add false positive
>>
>>106444724
I'd scrap the whole fn bullshit, instead i'd use something more consistent with the rest of the language:
fn hello(foo: f32, bar: &str) -> usize { ... }
static hello : (f32, &str) -> usize = |foo, bar| { ... }
// Or if thgey decide to add automatic type deduction for static:
static hello = |foo: f32, bar: &str| { ... }

Function are dubbed 'pure', however they capture their environment, just like closure. It just happens that the environment of a function is non-mutable so they would seems to have no side-effects, but everyone who's ever used LazyLock, LazyCell etc.. would know that this is not true

IMHO, this is more semantically correct and in-line with the rest of the syntax in rust.
>>
>>106448979
people don't pick languages for fun, if you had a job you'd know this. anyone who build web frontends is going to use javascript one way or another. if you do graphics, video games, or anything that requires harnessing the gpu, you're realistically gonna have to use c++. rust still has very poor support for opencl/openacc/cuda, and given the headache it is that to call c++ code from rust (an actual nightmare, especially if c++ doesn't take ownership of what you give it).
>>
>>106435392
your c++ example is overengineered
>>
>>106435392
ewww oop
>>
>>106437173
The faggot:
>heh, you got filtered by dildos
>>
File: cpphad.jpg (274 KB, 1280x720)
274 KB
274 KB JPG
>>106435392
i fixed the c++ version
>>
>>106450965
>not making Shape purely virtual
you're unironically ngmi
>>
>>106450702
(assuming this is rust code)
>negative traits)
this is a clear case of "specialization", not "negative traits".
specialization has been implemented since forever, but not stabilized. the original feature was unsound. so things landed at the "min_specialization" subset which is supposed to be sound.
this is used a lot in std (especially for performance reasons). and pretty much everyone who actually writes rust code is aware of it.
>>
>>106450647
Actually I know more about Rust and C++ than you ever will. Why have you not responded to this >>106441792 yet?

Let me guess, you are out of arguments and you have to resort to calling people "trolls" in order to save your face. Embarassing.

I am going to give you the same treatment as bruce and let you have the last word out of pity. You are pathetic and you will never make it.
>>
>language x is better y becau-*snips penis* FWIIIIIIIIISSSSSSSSSSSSH
>>
>>106451246
Dimwitted, low-IQ, lying troll Rust evangelist, you do not even pretend to make sense. Off yourself.
>>
File: rust.png (114 KB, 627x722)
114 KB
114 KB PNG
https://materialize.com/blog/rust-concurrency-bug-unbounded-channels/
https://media.defense.gov/2022/Nov/10/2003112742/-1/-1/0/CSI_SOFTWARE_MEMORY_SAFETY.PDF
https://bpb-us-e1.wpmucdn.com/sites.gatech.edu/dist/a/2878/files/2022/10/OSSI-Final-Report-3.pdf
https://archive.ph/uLiWX
https://archive.ph/rESxe
https://lkml.org/lkml/2025/2/6/1292
>>
Jeremy Bicha.
>SEX BAT BY JUVEN/VCTM UNDER 12; F.S. 794.011(2) (PRINCIPAL - 2 COUNTS)
Pedophile.
Rust developer.
PPA for Rust.
https://launchpad.net/~jbicha/+archive/ubuntu/rust

Mental health, pronouns and alter egos are at the very least trends in Rust. Also as the community Rust Discord server goes.

Hector Martin.
Insisting that Asahi Lina is not his alter ego.

https://aturon.github.io/tech/2019/06/25/back-in-the-saddle/

https://fasterthanli.me/articles/state-of-the-fasterthanlime-2024
https://fasterthanli.me/articles/that-health-is-mental
>>
>reddit spacing
lmao
>>
>>106451303
https://wiki.ubuntu.com/JeremyBicha
>I am a United States Navy Veteran and spent 2007-2010 living in Bahrain. I currently live in Florida. I joined Canonical in 2022 but my Ubuntu story started much earlier.

https://wng.org/articles/the-high-cost-of-negligence-1617309216
>Florida prosecutors weren’t forgetting: The U.S. Navy discharged Jeremy, and when he reached U.S. soil, authorities arrested him. He eventually pleaded no contest to two counts of sexual battery on a child under 12 while he was under 18. His defense attorney asked for less than a year in the county jail. The prosecutor asked for 15 years in state prison.
>>
Why does C attract so many mentally unstable schozoids?
>>
>>106451366
You misspelled Rust >>106451303 .
>>
>>106451407
>Schizo shit
Exactly what I am talking about
>>
>>106451415
Why do you call truth, including clear sources, "schizo shit"? Are you schizophrenic yourself?
>>
>>106435392
You're using inheritance for no reason. There are very, very few reasons to use inheritance in C++. Just because a language has a feature, doesn't mean you should use it.
>>
>>106450702
I was asking about Beef, not Rust or C++
>>
>>106450633
>In Scala and OCaml, it is easy to differentiate between the function declaration or definition, and the return type.
If you can't differentiate between the function declaration or definition, and the return type in Rust then I don't know what to say. Git gud
>>
>>106450791
>static hello : (f32, &str) -> usize = |foo, bar|
That's convoluted and hard to read lol
>>
>>106451827
i think it's not, because function are static constant variables. this syntax lines up perfectly with the rest of rust's syntax. also functions capture their environment, unlike just like rust's closure. even in rust, functions are not pure
>>
>>106451812
Inept, deceitful, incompetent, low-IQ, retarded troll, off yourself.
>>
>>106451879
>I can't read basic C-like syntax
>but you are the low IQ
Kek
>>
>>106451847
Yeah, and it's still much more convoluted and harder to read than fn name(arg: type) -> return. Splitting argument names and types into different places is pants on head retarded
>>
>>106451894
Your lies make zero sense, nitwit buffoon of a Rust evangelist troll. Off yourself.
>>
>>106451912
>incomprehensible seethe
>>
>>106451900
that's due to static not yet supporting type deduction from it's init stmt. if they add that feature. then it would be really easy
>>
>>106451916
That describes your trolling, not my posts, retarded, incompetent, dullard troll. Off yourself.
>>
>>106451086
that was taken from OP code
>>
>>106448415
If you want to disguish that, sure. But it's not really necessary. Most programming languages don't.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.