it's unironically my favorite syntax. Supposedly this makes me autism

>>17702 syntax hate is always junior talk. the way they parrot that shit, you would think it's Uiua-level or something. now that's some proper autismo.

>>17701 (OP) I didn't. I stay with C for philosophical reasons and C++ for IRL practical ones.

>>17710 rust is much closer to C philosophically (whatever that means) than C++, or any other mainstream language for that matter (yes, even go)

>>17701 (OP) I thought rust could be a good replacement for C But in the end, rust is just an even more hellish python. Riddled with extension middlewares and littered with the corpses of a thousand projects where the dev got bored but also couldn't play nice with anyone else. The future is bleak.

>>17701 (OP) I can't code I just think it's fun how it goes snibbidy snab

>>17711 >Rust is closer to C No it's not. It has its own package manager. It has its own build system. It removes freedom from the programmer because "we know better than you what you want to do". It embeds it's own paradigms into the language. It requires static linking which in itself reintroduce classes of vulnerability that we thought were gone since the 90s. It grows and bloats more and more with every new version. The language is so complex that it only has one compiler that itself takes about 24 hours to build on a decent machine. It was made by Pozzilla because they can't code. It's made by people who can't code in C, don't understand C, therefore became C++ Devs by default, yet have the audacity to come to real C devs and tell them it's a replacement for C. You Will Never Be a C Programmer.

>>17750 >You will never be a C programmer Yeah but isn't that the point?

>rust thread without "muh trannies" spam is india rangebanned here?

>>17750 >It has its own package manager. not language >It has its own build system. not language >It removes freedom from the programmer because "we know better than you what you want to do". a language is by definition a set of rules. it can be argued that types "remove freedom from the programmer". repeat with everything else. you couldn't go three sentences without exposing yourself as a complete nocoder, and a very retarded one at that. >It embeds it's own paradigms into the language. not doing that => multi-paradigm => big language => the opposite of C another show of retardation. >It requires static linking which in itself reintroduce classes of vulnerability that we thought were gone since the 90s. it neither requires static linking, nor there are "classes of vulnerabilities" related to this. >It grows and bloats more and more with every new version. true for any language with new versions, *including C*, unless a language guardian requires "removed features >= added features", which is something that doesn't exist in the real world. >The language is so complex that it only has one compiler that itself takes about 24 hours to build on a decent machine. another comment where literally everything written is wrong. the language doesn't have one implementation (mrustc). the language is getting a second *full* implementation (gccrs). building satge0+stage1 compiler literally takes X minutes (as in, a single digit of minutes) on any half-decent desktop from the last decade. not only you are a nocoder. you never even compiled anything in your life. >It was made by Pozzilla because they can't code. more nocoder retard talk >It's made by people who can't code in C, don't understand C, therefore became C++ Devs by default, yet have the audacity to come to real C devs and tell them it's a replacement for C. more retarded nocoder talk with the predictable language-as-personal-identity give away. >You Will Never Be a C Programmer. same as above, and a perfect closing to this show of retardation. i would tell you to share c code. but that would be bullying at this point, considering a retarded llm wouldn't have been this nonsensical if it was the author lol

>>17701 (OP) I still reject rust simply because what we already have works.

rust looks cool but I don't like having bloated binaries and a package manager to build a low-level program. just that, I really don't have a manifesto about it.

>>17773 >bloated binaries binary size is not a real issue in most use-cases, including all desktop and server ones (yes, including low-speced ones). many people just don't understand the real implications. and in any case, you can have small binaries with rust. so you have the choice if you want to continue in your false beliefs: https://github.com/johnthagen/min-sized-rust people targeting *truly and relevantly* constrained environments already know what to do, and how to do it. >package manager if you're building something with dependencies, you're using a package manager (or acting as one, doubtful). the fact that it's a part of the build tool, and the whole process is streamlined, is an advantage, and a daily experienced one at that. no matter how hard some choose to pretend otherwise. and in any case, you can skip cargo and use rustc directly, or go full tard and use another build tool with rust support like meson (yes, they support building with dependencies too).

>>17767 that's a minimal requirement for the definition of "works" you're using. what language doesn't "work"?

>>17765 the vibe is infinitely better without them, isn't it? lol

>>17793 I mean the tools we have that are already written in C just work. We should be improving what we have instead of re-inventing the wheel. The only reason you'd want to rewrite something in rust is if you have ulterior motives. I see no good reason for rewriting everything in rust.

>>17829 rewriting *everything* in rust is a meme. and talking conspiratorially about a handful of "rewrite" projects reeks of tech illiterate retardation. and none of this has anything to do with the language anyway. and believe it or not, most rust code (as in >99%) is not a rewrite of something. shocking, i know. other "shocking" facts: the handful of "rewrite" projects are not done by some single "ominous" entity. * you are still allowed to improve tools written in C, or any other language. have at it. although i'm not sure what's to improve since they supposedly "just work".

>>17839 strawman, I accept your concession.

>>17765 no

>>17702 I really appreciate Rust for forcing me to confront problems my patterns have vs being ignorant of them until they cause a problem. It's not the final be-all end-all for me, I'm currently looking at Gleam and the Erlang ecosystem. I think a happy medium would be a Gleam app with low-level socket interfacing or buffer interfacing code being kept as Rust using the Rustling NIF system.

>>17750 >It requires static linking That's not even true, dynamic linking is completely possible in Rust.

>>17765 To my knowledge, yes. And Israel

>>17765 So was most of the Rust hate coming from Pajeet streetshitters who can't into Rust because of skill issues?

>>18045 /g/ or the majority of it was basically amerijeet culture. an unholy marriage between /pol/-style ameritards, and 12-22 year old "edgy" unintelligent jeets. i write that and i'm technically american.

>>17701 (OP) Is "why would I need to use that" part of an anti rust psyop, since it's not something most people would need to use most of the time? Most hobbyists just write toy programs, and in industry people will follow what's already established anyway

Hey guys, wondering if anyone can tell me what style.rs is for in rust/src/tools/tidy/src, I see it searches for problematic "magic numbers" but I'm not sure when it calls this or why.

I hate trannies and I hate the culture the language comes with. The language itself is good, but it's not an overhaul of programming and it has brought with it a culture of moralism over "memory safe languages" to the point where there's an implicit moral judgement on using C. Just look at channels like LowLevelLearning on YouTube that act like creating secure software in C is somehow impossible and revolutionary. Also, most things don't need to be written in Rust. Most networked applications should be written in Go unless you need what Rust offers since Rust just takes longer to write. Rust is a good replacement for C++, and I hope that it fully replaces C++ in the future. Fuck trannies. I still use Rust.

>>18090 You are a contributor to the rustc compiler. You want to submit a patch that's going to be used by other users of the compiler. There are hundreds of other developers on this compiler, and they've all agreed to set of common standards for the compiler's codebase. The person reviewing your patch runs an automated tool to check compliance between your patch and those standards. One of those standards is "don't use any fucking magic numbers". The code that ensures compliance with that standard is in style.rs

>>17711 If you come into Rust from a C++ background, you will understand far more of Rust's design philosophy than if you come in with just a C background. Someone who understands only C and not C++ will lack background knowledge on RAII and smart pointers, on generics, on move semantics, and so much more. >>17750 >It has its own package manager >It has its own build system Neither C nor C++ have their own package manager or build system, therefore it is nonsensical to use Rust having a package manager to suggest that Rust is more like C++ than C. >It removes freedom from the programmer There is exactly one feature from C that Rust does not have an equivalent of, and that is varargs. Rust prefers macros to perform compile time checking of variable arguments, since format strings in C are a known cause of vulnerabilities. Everything else you think is removed is perfectly valid Rust. Having to type unsafe is not a removal of freedom. You don't like it because it has the aesthetics of asking for permission when in reality the unsafe keyword accomplishes nothing other than documentation. Specifically, it is documenting that a particular section of code cannot be verified by the compiler.

>>18575 I happen to be a person who came to Rust from a C (and no C++) background. >lack background knowledge on RAII and smart pointers, on generics, on move semantics, and so much more. so two things to point here: maybe with the exception of smart pointers, those are things you do in C, but you do them manually, and without type safety. you manually release resources (free, close, ...etc) instead RAII, and you manually cast ///void*\\\ pointers instead of using proper generics, ..etc. with move semantics, it depends on your data-sharing architecture, but it is a pattern that also exists where you pinky-promise yourself not to use data after sending it (implicitly or explicitly) to another thread for example. so with that view, and unlike c++, rust for c developers often doesn't require much of a paradigm shift. just a different discipline when writing code. for example, the way rust encourages static dispatch with generics is much closer to c than using OOP+vtables in C++. and with that in mind, let's go to the second point. while some of the features you mentioned share the same name with features available in c++, the design, implementation, and integration of the feature can be significantly different. we actually had this problem in rust support forums for years. people coming from c++ had to basically unlearn everything from their c++ past to do rust properly. we didn't have this problem with C people, of which i myself originally was one. the only initially challenging thing to people coming from c, or any other language, is (rust's) move semantics and the borrow checker. and even that is overstated. not to mention that it quickly becomes the favorite thing about the language for people coming from a c background. oh, that probably saved me a week of debugging quickly becomes a common utterance.

>>17701 (OP) Its syntax looks so disgusting I will probably never bother to learn it.

>>18587 I think you might be confusing implementation and abstraction. Concepts of RAII, move semantics, and generics are of course going to be implemented differently in C++ and Rust. But as an abstract language feature, these are held in common. C does not have these as an abstraction. That you can implement yourself the features that are abstracted over does not mean that an abstraction exists. I think the problem I'm trying to underscore here is that a lot of C programmers that I've observed (perhaps not you, since you've managed to adapt well to Rust) struggle with the higher level abstractions in Rust. They might see an error from some vec or string being passed to two different functions and complaining about use after move, and get confused because they may not grasp what "move" is at a high level, even if they would understand things if they had been operating with just pointers at a low level. I also regularly see complaints about them from the heavy amount of syntax used in generic functions, which are all fairly common in C++ code. You do have a point that many C++ programmers can still struggle when transitioning to Rust, since the implementation details differ in certain areas. To be good in either language, you need to both being able to think in high level abstractions AND in low level implementation details at the same time. For C, there's not much opportunity for abstraction, giving it a common impression of being simple (although the trade-off of simplicity is having to write a lot of boilerplate that may contain mistakes). Meanwhile people coming from some Python or JavaScript background will struggle with ownership concepts as well because they don't understand that there's a difference between, say, a string literal stored in .rodata and a string buffer stored on the heap.

>>18572 Okay but why can't you use these magic numbers? Reading through it further looks like those binary numbers are converted, and then they run a regex with some substitutions, so the original magic numbers don't matter?

>>18605 Because that's the stylistic conventions they've chosen for the project. Let me ask you something though, why do you care? Do you personally have an interest in submitting patches to rustc or cargo? Do you regularly find yourself using popular magic number constants in your code like 0xDEADBEEF or whatnot? Can you see a strictly necessary use case for magic number constants in the rustc compiler?

>>17701 (OP) I did not need a psyop, I tried using Rust

>>18572 >>18605 >>18618 NTA, but it really is the usual tranny shit, don't even play devil's advocate >>18618 I looked at the consts and they're all versions of "babe, dood, boobs, balls", so some tranny got very triggered about those hex spelled words and tried to make the linter avoid it. There's no other explanation since it's just a series of popular magic values and they were triggered by then, you can especially tell this because they call these words "problematic" and they hide it as decimal. It's just hilarious how thin their cheeks are. There are plenty of other silly magic numbers and their list is not anywhere exhaustive. I've seen some of them like 0xDEADBEEF 0xCAFEBABE used in Microsoft code at least (heap allocator maybe?), so you know what they were bothered about lmao Even if you don't use them in the code, code that has to interop would, so you'd be forced to "hide" it from the linter, which is quite some autism.

>36 >20

>>18933 So as the comments in their code suggest, they're wasting time scanning the entirety of your code for over 2k variations of these hex codes or "needles" as they call it, just because they're offended by something old developers found funny years ago? Judging by the error message that it throws if it finds one, they don't have issue with other potential magic numbers, or arbitrarily random hex codes now it makes sense why they obfuscate the purpose of it, hiding the magic numbers as binary in the list, referring to it as "needles", and throwing an error that only tells you "magic number bad, use 0x12345678 instead", they want to fun police without anyone realizing it I wonder just how much extra time this adds to compilation

Can someone move this thread to /trap/?

>>17701 (OP) You mean the shit that's made most of the internet slow as fuck?

>>18945 >your code no. how are you people reliably this retarded. anti-rust nocoders always give uncoachable vibes, in whatever it is that they do in life, which definitely doesn't involve coding of any kind.

>>18959 do expand

>>18996 oh sorry, I forgot to use inclusive language >they/thems code

>>17713 What would be required to make it better?

>>18933 >Even if you don't use them in the code, code that has to interop would There's nothing in the rustc source code that would reasonably need to interop, at least directly, with anything other than .rs files. Its job is to read, tokenize, and parse Rust source code, transforming it into an intermediary format once all correctness tests are performed. Once in that format, it is the job of third party libraries (LLVM or perhaps cranelift once fully implemented) to turn it into an executable. If the front end of the compiler (which is the thing that's getting linted) is checking for the presence of magic numbers in binary files, that is scope creep.

>build a statically typed language >include a static analyzer in the compiler >spend years shilling your "memory safe" language that leaks memory >still has compiler bugs that cause segfaults >compiler is self-hosted but uses nightly features making a bootstrap impossible >repeat the mistakes of npm and pip because faggots can't into packaging >cuck licencing out of hand Can you niggerfaggots kill yourselves faster so everyone can get back to using sane tools. Debian labeled rust shit as unmaintainable because it is Gentoo users are forced to use rust-bin because compiling rust takes a decade and still OOMs

i didnt but then again, i've forgotten how to code now

>>20262 GO BA.... oh wait, honeypot /g/eetard central is dead. i wonder why

>>20289 I'm sorry u snibbity snabbed ur pee pee off mr anon

I want to learn Rust so bad, but I just don't have a personal use case. What I want to achieve for my personal life that I haven't set up yet: >home server in a k3s setup that may or may not use several physical machines >home assistant based on whatever replaced Mycroft as an open source alternative to spyware >home automation for at least one thing that I can control aside from lights Is there any use case hidden in those that could be addressed by self-made software in Rust? I start to fantasize about replacing the google sheet formulas my coach set up for my gym plan with software. It feels like I'm reaching for a goal because I'm not having any ideas on my own. What would you do in Rust?

>>20297 >home server in a k3s rust or not, you need to learn and tinker with lower-level stuff (embedded, system) for a while to un-tard yourself from having such thoughts.

C feels much comfier, and Rust's syntax is schizo.

I don't mind Rust the language but Rust the community is a cult that is lead by the nose by corporations to replace GPL software, see uutils for the latest example gaining steam.

>>19081 The runtime might, I'm not well-versed into where this linter is applied, but are you saying their policy is to not apply it to the runtime as well?

>>20534 The linter is a static analysis tool. It is run on the source code of the rustc compiler. It checks for deviations from the style conventions of the project. Aside from the "problematic consts" thing, it also checks for things like "don't have lines that are very long" or "don't use tabs over spaces". It is not meant for any sort of runtime checking. It's possible that rustc will link against a library that incorporates these constants in order to interface with some third party binary format. That is not a rustc problem. The concerns of rustc are its own intermediary formats. And the rustc team has decided that in their intermediary formats, they should not be using popular magic numbers. So they check for them in the same script that checks for "don't indent with tabs". Why they do this, I'm not fully sure. Maybe they think DEADBEEF is distasteful to read in a codebase. Or maybe there's a more practical concern, like making sure some rlib file doesn't get confused for a Java class file by any third party tools because someone thought it cute to put CAFEBABE as the first four bytes of the file.

>>20297 If you're just looking for something to do (with Rust): genetic algorithms are pretty fun to toy with. An advantage of experimenting with GA in Rust is that it's easy to convert hack-ish single-thread code to multithreaded with rayon.

>>20504 you are literally more retarded than the people you think you're complaining about. because you're making technical decisions based on supposedly associated people with certain software, except both the supposed people don't exist as a single entity, and who decides to use a language has nothing to do with the language itself. otherwise, you should stop using C right now, because i personally had developed public projects written in C, and contributed to a couple of libraries used, one way or another, in every device you own with an operating system on it.

>>20571 Holy melty. It's a fact that almost the entire Rust ecosystem is written in BSD or MIT and that most Rust projects are rewrites of GPL software. I'm judging the corporate glownigger language for what it is, a trojan horse to get the GPL out of linux userspace.

>>20579 >It's a fact india rangeban can't come soon enough

>>20633 >you're a j-jeet Retard, Rust is promoted by corporations because it means the jeets you're training to replace you will fuck up less. That aside, Rust is plagued by cuck license trannies and funded by corporations for the explicit purpose of hurting the GPL. Why else would uutils be MIT licensed and rapidly adopted by corporate distros, despite not being a full drop-in for coreutils?

>>20633 Snippity snap, this rust devs a trap!

>>20579 The entire Rust ecosystem consists of libraries that are intended to be linked against statically. Many use features (generic types/functions, proc macros) that could not be shipped as part of a dynamic library because they are not incorporated into a program at link time. If they were to be licensed as LGPL instead of BSD or MIT, they could only ever be included in open source programs because there's no way to change out a static library from a compiled executable. The GPL is fine for applications, but no one is going to want to use your language if the libraries have such viral requirements.

>>20682 MPLv2 is used a lot in Rust too (e.g. servo), which is a modern LGPL. It's not all MIT, not that the retards know anything about what we're talking about here.

>>20682 Static linking is 90s brain damage that's making a comeback with MIT and BSD licensing because some people never got over the lawsuits. It's not a selling point of rust, it's another (optional) expression of linux hostile cultism like the fixation on licensing. >The entire Rust ecosystem consists of libraries that are intended to be linked against statically Yeah microdependency hell each maintained by a different guy. librsvg has ~280 crate dependencies, oxipng has ~75 and those are just the mandatory rust dependencies on my system. Oxipng alone has double the dependencies as every go package on my system combined (lf, kitty, dnscrypt-proxy) except golint-ci. Add that and it's equal. Cargo is jeet street like npm.

https://github.com/Gankra/cargo-mommy >Mommy's here to support you when running cargo~ https://github.com/Shadlock0133/cargo-vibe >Cargo x Buttplug.io Rust is a very serious language for very serious people who totally aren't porn-addicted crossdressing pedophiles.

>>20698 >Static linking is 90s brain damage Actually, genuinely retarded nocoder inverting reality Docker exists just to cope with the hell that is shared libraries

>>20704 I retract my funny anti-rust posts, you're a nigger and you don't belong here, get back to your faggot board with built in datamining, snibbity snap your neck while you're at it

>>20709 >nocoder What this means when a retarded nigger from nu/g/ says it is >you're not a software "engineer" Thank god. Most of you are indian and the rest have indian bosses. I code for fun when I feel like it. And no, I don't like C either. >static linking Is cancer that creates a hell of mismatched capabilities and security vulns in your system packages because maintainers are lazy fucks. You're defending it because it's part of the Rust Paradigm™, if dynamic linking was the community default you'd be defending that instead. >>20710 >he thinks the sharty owns nazijaks kek kill yourself 4troon. The sharty is a zoomer shithole I don't use, but it's still better than Gay Louis Irwin's cuckshed, which you'll be going back to next week.

>>20713 >A bloo >A bloo bloo >3 miles of text to say nothing but "I am a faggot homosexual and need to kill myself" Get off my board you sniggerdly cuckafuck

>>20716 >t-take the mean bald man away now!!! kek. Must be hard not being able to cry for bans to your fellow pedophiles on discord.

>>20718 I can't help but notice you didn't read most post, would you like some help killing yourself or can you manage on your own? we're here to help cater to your special needs, the easiest way is with helium tanks and a blanket, your mishapen body won't even be able to tell the difference! just a few minutes and it's off to soysoy land or wherever faggots go when they die Btw I'm not reading your posts anymore, if you reply I'm just going to assume you need more help killing yourself

>>20713 Even cat-v and the designers of Plan-9 disagree you moronic clown https://harmful.cat-v.org/software/dynamic-linking/

>>20722 kek 4troons are so easy to troll. I know it's a shock to a newnigger like you but there are other imageboards besides 8gag, 4kidz and your latest boogeyman. You are a pathetic nigger for getting triggered by 'jaks because some sharteen took down 4kidz, when it's been Weekend at Hiroyuki's for a decade. Which child groomer in these pics is you?

>>20726 Oh no anon, you couldn't even huff helium correctly, that's terrible, are you able to walk or is your genetically broken body unable to lift its heavy frame off your moist and smelly bed? If you can walk I recommend finding the nearest tall bridge, a quick jump should bring you to soy soy land even if you're a discord user and struggle with simple tasks Btw why did you snip your pp off?

>>20725 >life considered harmful and the designers of an OS no one ever used agree with me The absolute state. If any of that word vomit (yes including the Carmack quote) was correct, dynamic linking wouldn't be the default on linux. I'm not reading the rest, you are a transvestite pedophile in a child grooming cult around a technically good language.

>>20727 >no u kek. How hard are you hitting that report button, child rapist?

>image swallowed kek 4jannies must be DDOSing the site again.

>>20729 Why do you vote Dems anon? >>20728 >Mfw I've been calling rustroons trannies in the thread because it's funny realtalk I don't understand the joke here at all, it's just edgy for edgy sake in a retarded way Oh wait, you're actually trying to take advantage of disaffected youth, that's fucked https://desuarchive.org/_/search/text/integrity.wasm/ this exists for anyone who wants the lowdown on sharty, it's a glownigger op, if it wasn't painfully obvious already Also stop fucking kids anon it's bad for your penis >>20731 You just don't belong, bye bye

>>20732 >You just don't belong, bye bye You're a gay nigger straight from orange reddit and no amount of crying about drawings is going to get me to stop posting them. >it's just edgy for edgy sake in a retarded way Imagine being a faggot newnigger from 4kidz who wasn't on /tech/ and calling people glowniggers because it's le funny shitpost off main, and thinking you have anything to do with the culture. You probably cry about stormfags when janny has your back on 4groomers.

>>20736 https://desuarchive.org/_/search/text/integrity.wasm/ >Literally a glownigger operation >public knowledge >miles of text seething and crying No amount of crying is going to reattach your penis anon, stop fucking kids anon >t.

*who wasn't even on /tech/ It's hilarious that as soon as the 'jaks come out, the pedophiles get together and stop pretending to disagree over rust. Shitting on it or wayland or whatever the latest meme to hate is, is just le epic joke for newfags to fit in. They only come to IBs looking for kids to rape and not for discussion without their upboat faggotry and powertripping groomer mods.

>>20736 >Spamming off topic posts with memes that are not board culture >UGHH THOSE POWER TRIPPING MODSSSSS Kek the jannies are the heroes for once, double their pay immediately

>>20739 Imagine being a pedophile nigger like you, seeing the sharty under your bed because it took you away from the tender mercies of invisibro and grooming kids on /r9k/ and /soc/. You got here last week after seeing a link on twitter and you're trying to gentrify neo-8chan kek. >>20744 Keep hitting that report button 4cuck.

>>20749 >pedophile ree ree Why do you vote Dems anon?

>>20751 That image is genuinely the most disgusting thing I've ever seen posted on any site named 8chan. Pic related, you are reanimation. >vote dems As if being an unironic 4cuck here isn't bad enough, now you pivot into ZOG worship.

>>20752 Sneed sneed sneed sneed sneed sneedsneed sneed sneed Sneed sneed sneed sneed sneed sneedsneed sneed sneed Formerly chucks formerly chucks, chucks fuck and suck https://www.youtube.com/watch?v=xFByuYF0Z50 Its bad to vote Dems anon stop it

>>20756 I'm not even going to bother with the 'jaks, you're a nigger invader who can't go back to 4chan quickly enough.

>>20752 It's a subtle joke, the sign says sneeds feed and seed, FORMERLY CHUCKS, chucks fuck and suck!

>>20760 Another 4troon mindbroken.

>>20763 >He doesn't get the joke Formerly chucks anon, don't you get it?

>>20765 The only joke here is newfags who think simping for 4chan has even been the culture outside of niggertits.

>>17701 (OP) lmao the anti-Rust (((psyop))) useful /g/diots have arrived with their street-defecation-level contributions. i guess we should congratulate 8chan since even small boards like /t/ gained (((under watch))) status.

>>20749 >He doesn't know >>20766 You sound like a city slicker, and we're all out of seed boy' >>20767 I think soytroons are just unhappy no one wants to go there, I've heard they have AI setup to keep boards active

>>20768 It's actually kind of funny that all you can do is post stale memes and anime while hoping janny shows up, because 4chan has been a culturally dead website since 2014. Definitely nothing to do with #janiteam or the other shit you missed out on.

Anon, the only way to respond to cancer is with AIDS

>4cucks ran away Oh well. Still going to post these for the newfags before I go. >full #janiteam leak https://litter.catbox.moe/g8agt6.7z

>soycuck anon demands (you)'s Sneed

>>17701 (OP) Rust will never be a functional language.

<masterchan is our new safe haven m8 its not 2014 anymore