/tech/ - Technology★

how come hes smart enough to make rust but stupid enough to believe in antifa?

>>869616

Steve Klabnik mostly writes documentation.

>>869618

and btw he fucking sucks at it. The first edition of the book is meh at best and the second edition is still not even close to being finished.

Thank fuck Steve is alive. I was getting worried that you might have been beheaded by Ahmed.

>>869616

The actual Steve Klabniks job is to write the Rust book(which isn't done and has been dragging along for multiple years), posting on social media and rewriting the documentation thing in meme.js.

>>869627

>go to the bother of making a new OS

>reimplement the garbage that is unix

lol if this doesn't tell you everything you need to know about Rust.

>>869589 (OP)

so is it really safe now?

or there is still some UB in "safe" subset?

>>869635

https://github.com/rust-lang/rust/issues/10184

https://github.com/rust-lang/rust/issues/25860

https://github.com/rust-lang/rust/issues/27060

https://github.com/rust-lang/rust/issues/27282

when?

>>869633

>Redox is inspired by previous kernels and operating systems, such as SeL4, MINIX, Plan 9, and BSD.

>>869635

>>869637

Rust is and always was safe. It is rustc, the compiler, which has bugs that allow memory unsafety. But they will be fixed soon. The reason why those bugs existed so long is that the Rust developers decided to rewrite parts of the compiler. These rewrites will bring yuge improvements. You can test some of it in nightly Rust btw.

>>869639

Unix

>>869645

Nigger

I'm unironically curious and want to learn rust in my free time. What's the best place to start ?

>>869647

>>>/suicide/

>>869647

https://doc.rust-lang.org

https://rustbyexample.com

>>869646

lol do please tell me about your non-unix unix-like OS and your webdev systems language.

>>869654

>unix

it isn't

>webdev

nodev detected

stop shitting up my thread, anti Rust shill

>>869659

You can't shit up an already-shit thread, though.

>>869661

kill you're are self

>>869659

<Redox is a Unix-like microkernel operating system written in the programming language Rust.

you should go back to pretending to be retarded

>>869666

you should stop talking about irrelevant shit in a Rust thread

>>869639

>Rust is and always was safe. It is rustc, the compiler, which has bugs that allow memory unsafety

It's like we have an alternative to rustc in this Universe right now, or can interpret Rust code in our brains at comparable speeds.

Nice evasion.

>>869627

>>869633

>>869639

>>869645

>>869646

>>869654

>>869659

>>869666

I think what you're ultimately referring to is that despite being unix-like, they don't conform to POSIX if they feel that their way of doing things is better.

From a page on their shell:

>Why Not POSIX?

>If Ion had to follow POSIX specifications, it wouldn't be half the shell that it is today, and there'd be no solid reason to use Ion over any other existing shell, given that it'd basically be the same as every other POSIX shell. Redox OS itself doesn't follow POSIX specifications, and neither does it require a POSIX shell for developing Redox's userspace. It's therefore not meant to be used as a drop-in replacement for Dash or Bash. You should retain Dash/Bash on your system for execution of Dash/Bash scripts, but you're free to write new scripts for Ion, or use Ion as the interactive shell for your user session. Redox OS, for example, also contains Dash for compatibility with software that depends on POSIX scripts.

So they keep dash around for compatibility's sake, but their main shell deviates from POSIX for the sake of innovation.

As far as the actual OS goes, one of their ideas is "Everything is a URL":

>"Everything is an URL" is an important principle in the design of Redox. Roughly speaking it means that the API, design, and ecosystem is centered around URLs, schemes, and resources as the main communication primitive. Applications communicate with each other, the system, daemons, etc, using URLs. As such, programs do not have to create their own constructs for communication.

>By unifying the API in this way, you are able to have a consistent, clean, and flexible interface.

>We can't really claim credits of this concept (beyond our exact design and implementation). The idea is not a new one and is very similar to 9P from Plan 9 by Bell Labs; a similar approach has been taken in Unix and its successors.

>With "Everything is a file" all sorts of devices, processes, and kernel parameters can be accessed as files in a regular filesystem. This leads to absurd situations like the hard disk containing the root filesystem / contains a folder named dev with device files including sda which contains the root filesystem. Situations like this are missing any logic. Furthermore many file properties don't make sense on these 'special files': What is the size of /dev/null or a configuration option in sysfs?

>In contrast to "Everything is a file", Redox does not enforce a common tree node for all kinds of resources. Instead resources are distinguished by protocol. This way USB devices don't end up in a "filesystem", but a protocol-based scheme like EHCI. Real files are accessible through a scheme called file, which is widely used and specified in RFC 1630 and RFC 1738.

>>869671

>As far as the actual OS goes, one of their ideas is "Everything is a URL":

> their ideas

it is not something new. even Android has something similar, and it took it from plan9 or something I dont remember.

>>869670

Alternative Rust compiler: https://github.com/thepowersgang/mrustc

Nice anti Rust shill post.

>>869674

>mrustc works by comping assumed-valid rust code (i.e. without borrow checking)

it is even less safe.

LOL WTF dude, did you even read the fucking README from your link?

>>869679

calm down anti Rust shill. I didn't claim mrustc to be safe.

>>869679

Compiling is different from type checking and borrow checking, dumbass.

>>869693

>>869682

the point is that there's no safe implementation of Rust right now.

>>869700

Very nice anti Rust shill post. I rate it 8/10.

>>869682

>>869700

anti Rust shills detected.

it is safe.

>>869707

>>869702

Perhaps you have any facts that counter my argument?

>>869976

What argument? That rustc has a few bugs? That is a fact and can't be countered.

>>869982

That the lack of safe imlepmentations impiles the langauge can't be called safe yet.

>>870010

You are contradicting yourself. The language is safe. rustc is not safe bacause of bugs. Prove me wrong or fuck off anti Rust shill.

>02/16/18 (Fri) 13:22:28 No.870015

>02/16/18 (Fri) 12:48:04 No.870014

>13:22

>12:48

>literally nobody posted in /tech/ for whole 34 minutes

>>870015

>The language is safe

this is a strong statement and needs a proof.

>>870019

https://www.ralfj.de/blog/2017/07/08/rustbelt.html

>>869627

Is Redox the FreeBSD killer?

<since linux is already dead

>>869700

>it's not perfect goy, come back to my shitty c plantation

>>870015

>The language is safe

Cool your jets nigger it's getting there but hur dur it safe is brainlet talk and shits up Rust which already has a faggity rep. 1 formal proof of a subset of Rust was done with grat success but that's a start not the end.c queers back to sucking your own 4" cock

>>870124

>is brainlet talk

You literally talk like a brainlet.

>>869618

>>869626

This, please don't present this rat-man as the face of the language when all he is is a verbal parasite.

hey rustfag kannst du mir nen job beschaffen?

>>870176

nee, bin selber arbeitslos

https://archive.is/BtDaA daily reminder

>>869589 (OP)

> a tool that automatically can reformat your Rust code to some sort of “standard style.”

About time.

t. Ada

>>870180

Steve is willing (for other people) to fight to preserve his supply of third world dick

>>870180

uh i'll just keep using c thanks

>>870125

Off-by-one error redirects insult back at you C queer.

>>870180

These commie leftists (using computes and other devices of capitalism) are such cocksucking faggots. Hopefully Steve gets some documentation work done before being beat to death by the niggers he attempts to rile up.

>>870194

C is for cuck nigger.

what the fuck guys?

99% of these posts are >>>/b/ tier bullshit

can we actually talk about the tech instead of shitposting?

>>870207

If you've been here for more than a week, you know that that we're inundated with pointless Rust threads to an extent where there isn't much to say anymore. It's partly their own fault, for allowing the technicals of their language to be lost amidst the worthless SJW talking points espoused by a vocal section of their community.

>>870220

>worthless SJW talking points espoused by a vocal section of their community

thats just about every community in the normie world tho, i mean my opinion of it is meh, but it would be nice to see that shit ignored and have some decent tech talk on this tech board...

>>870239

That would be the dream. Politics is not technology.

>>870239

There was never decent tech talk on /tech/.

>>870176

https://www.facebook.com/careers/jobs/a0I1H00000LCTYYUA5/

>Software Engineer, Source Control

>Facebook's mission is to give people the power to build community and bring the world closer together. Through our family of apps and services, we're building a different kind of company that connects billions of people around the world, gives them ways to share what matters most to them, and helps bring people closer together. Whether we're creating new products or helping a small business expand its reach, people at Facebook are builders at heart. Our global teams are constantly iterating, solving problems, and working together to empower people around the world to build community and connect in meaningful ways. Together, we can help people build stronger communities --- we're just getting started.

>Facebook’s Source Control team is seeking an experienced software engineer with expertise in Rust or a similar systems programming language, to build and improve our next generation source control server. You will help design and extend Mononoke, our highly scalable source control server, optimised for serving massive monolithic repositories. Your work will be a critical part of the daily workflow of thousands of Facebook employees.

As a successful candidate, you will lead a team of engineers working on Mononoke, identify new use cases that Mononoke unlocks, and be instrumental in open-sourcing Mononoke and helping others across the industry to adopt it. Mononoke is written in Rust, so experience in Rust is desirable. A love of data structures and algorithms is a must. We are looking for someone who loves solving hard problems at scale.

>Responsibilities

>Proactively develop server-side source control software in Rust

>Lead improvements to underlying Rust code base

>Work with other teams at Facebook to realise the full potential of a highly scalable source control server

>Open source your work and help others across the industry to adopt it

>Minimum Qualifications

>B.S. or M.S. in Computer Science or related field, or equivalent experience

>Experience with systems programming at scale

>Strong communication skills

>Preferred Qualifications

>Experience with Rust

>Experience working on distributed source control software

http://andrewkelley.me/post/unsafe-zig-safer-than-unsafe-rust.html

Rust BTFO

>>877550

There is no difference between unsafe Zig and Zig. There exists no safe Zig. This clickbait blog post is just the creator of Zig desperately trying to get Zig onto Hackernews/Reddit.

Thanks for bumping my thread btw <3

>>877580

>There is no difference between unsafe Zig and Zig

Because there is no need to create a "safe" subset for a language that is already reasonably safe if the author is not acting maliciously. (and if we count malice, then no language could prevent intentionally malicious code)

Similarly as there's no "safe" Python or Java because no one needs that.

Unsafe Rust, on the other hand, is a footgun, as it was just demonstrated.

>>877596

>Because there is no need to create a "safe" subset

https://www.cvedetails.com/vulnerabilities-by-types.php

>Similarly as there's no "safe" Python or Java

Python and Java are memory safe. So yes, there is a safe Python/Java.

>Unsafe Rust, on the other hand, is a footgun

So just like C/C++/Zig?

>>877598

>Python and Java are memory safe. So yes, there is a safe Python/Java.

import ctypes

import sun.misc.Unsafe;

>>877598

>>Unsafe Rust, on the other hand, is a footgun

>So just like C/C++/Zig?

Better than C and C++ and worse than Zig

>>877598

>https://www.cvedetails.com/vulnerabilities-by-types.php

They aren't about Zig, are they?

>>877601

>import ctypes

>ctypes is a foreign function library for Python. It provides C compatible data types, and allows calling functions in DLLs or shared libraries.

So? This allows you to call shared libraries from Python. That doesn't make Python unsafe.

>import sun.misc.Unsafe;

>Unsafe

ok kid

>Better than C and C++ and worse than Zig

So still unsafe? Thanks for clarifying.

>They aren't about Zig, are they?

LOL. Are you trying to imply that Zig isn't a stillborn language?

>>877602

>LOL. Are you trying to imply that Zig isn't a stillborn language?

are you trying to imply that a language is only alive if someone is making a shitload of vulnerabilities in it?

>>877603

No. I'm trying to imply that nobody except for the creator of Zig is using Zig.

>>877605

And the proofs are …?

>>877612

https://ziglang.org/

>Zig in the Wild

>OpenGL Tetris

>i386 Operating System

>Pokémon Rom randomizer tool

>Micro:Bit Demo

>ARM Kernel

Hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm...

Really makes my thought noggins jogging...

I want the dylan language to live. ;_;

>>877616

define class <point> (<object>)
  slot point-x :: <integer>,
    required-init-keyword: x:;
  slot point-y :: <integer>,
    required-init-keyword: y:;
end class <point>;

disgusting

WE SIMD NOW BOYS!!!

https://doc.rust-lang.org/nightly/std/arch/

>SIMD and vendor intrinsics module.

>>878101

>unsafe

lmao

>>878107

>muh unsafe

Kill yourself anti Rust shill. Read this:

>This module exposes vendor-specific intrinsics that typically correspond to a single machine instruction. These intrinsics are not portable: their availability is architecture-dependent, and not all machines of that architecture might provide the intrinsic.

>>878107

the rust standard library has lots of unsafe blocks. unsafe is idiomatic.

One word that often falls when discussing the Rust community is “nice”. And yes, this is the result of active effort of a number of official and inofficial participants. Today I’m going to compare the Rust community with traffic.

There have been studies that show you need to direcly control only about 5% of cars to eliminate traffic jams (sorry, I’m not going to google the paper, trying to make a point here), and I believe the same applies to assholery in programming communities: If just 5% agree on being nice, they may sway the behavior of the community as a whole.

That is not to say everyone welcomes this kind of control. Imagine being in an almost-jam, trying to weasle through traffic, cutting off people left and right, only to find that a few cars before you, some cars coast, forming a slow-ish barrier you (and perhaps the cars before you) cannot pass. They’re slowing you down! You’d honk in righteous anger! What you don’t (and probably don’t want to) know is that those cars slow down to avoid a traffic jam, by keeping you from creating it.

(As an aside, I find that driving in traffic tends to bring out the worst in us. I’m unsure why that is, but I hear that people behave less well if they feel being in their private space, and most people count their cars in that category)

In a community the coasters being nice have a similar effect on those trying to weasel their way through, shaming and trolling left and right. People being nice offend those who don’t want to be nice themselves, and those people honk “SJW Police! Witch hunt!” in self-righteous fury. Lacking empathy, they think others are only nice to appear better than them, to make them look bad. Why else would someone waste the time and energy? Worse, with the backdrop of all this friendlyness, their weasling attempts suddenly starkly contrast. So they start to resent the “SJWs” on their high horses with their holier-than-you ‘tude.

By defending their “freedom” to bring everyone else to a halt, they’re telling you that them being at their destination five seconds earlier is more valuable than everyone around them not being stuck in traffic for another half an hour. I sincerely doubt the idea that those metaphoric five seconds benefit the community as a whole more than the multitude of half-hours wasted by being stuck.

This is not to say that everyone who blurts “Freedom of Speech” is an asshole. Some were just raised to believe that freedom is the biggest ideal and will reflexively fight everything that appears to curtail it. I personally believe this is misguided. Freedom of Speech is not Guarantee of Audience. I have yet to see any of those people speaking up when someone loud and obnoxious is thrown out of a restaurant -- yet by extension of the same logic this should also count as a free speech violation, right?

Anyway, enough of the rambling. The key takeaway is that the argument that a Code of Conduct keeps people from getting things done is completely bogus. On the contrary, it keeps people from keeping other people from getting things done. I’ll leave you here with a verse:

Let’s play a game & surprise folks’round you by being nice Who gets most smiles this way wins this game & the day Now go & apply this advice

>>879181

you're right about traffic but the analogy is shit and does not apply here.

>>879181

>The key takeaway is that the argument that a Code of Conduct keeps people from getting things done is completely bogus. On the contrary, it keeps people from keeping other people from getting things done.

Perhaps you can explain then:

Why all the drama happens in projects which have a CoC, while other projects just werk without drama?

If your post was true, it should be the other way round? Or do we live in a wrong universe?

>>879191

>while other projects just werk without drama

Can you prove that statement though? I can certainly disprove it for you: Libav

>>879198

CoC doesn't stop anyone from forking and deciding to isolate if the license allows to do so.

libav is just a fork, and all the "drama" is because a few people did not agree on some things. (This happens sometimes and it's just how is life.) Not because someone started bitching about diversity and white privilege.

The latter always goes with CoC. I have far more examples of that, but I think you already know about them.

>>879205

I don't understand what you are tring yo say. First you said that only projects with a CoC have drama and now you try to define drama as bitching about diversity and white privilege?

Also libav wasn't just a fork. Debian replaced ffmpeg with libav and called ffmpeg deprecated.

>>879219

>Debian replaced ffmpeg with libav and called ffmpeg deprecated

only because a "smart" kid from libav happened to be also an admin in Debian&Ubuntu.

it was reverted later, fortunately.

>>879219

>you try to define drama as bitching about diversity and white privilege?

if we talk about CoC, it is reasonable to talk about the kind of drama which CoC aims to solve?

>>879222

>only because a "smart" kid from libav happened to be also an admin in Debian&Ubuntu

So? It still is drama.

>if we talk about CoC

>Why all the drama happens in projects which have a CoC

No. We are not talking about CoCs. We are talking about your claim that drama only happens in projects which have a Coc. Which I have disproven and you can't accept because >muh CoC.

>>879191

>Why all the drama happens in projects which have a CoC, while other projects just werk without drama?

>what is grsecurity?

>what is bitkeeper?

>what is gcc ast?

>>879226

okay, maybe not only, but most of the relatively recent drama in FOSS projects happens in projects with CoC.

remember Mozilla, Drupal, https://github.com/opal/opal/issues/941 (this thread speaks for it all actually)

what else, I forgot, a quick search will bring up another couple.

>>879253

me in the background

>>869616

Really makes you think. Perhaps you are the dumb one and everyone should actually believe in antifa because they're right.

New blog post boys:

Rust's 2018 roadmap

Rust: 2018 edition

This year, we will deliver Rust 2018, marking the first major new edition of Rust since 1.0 (aka Rust 2015).

We will continue to publish releases every six weeks as usual. But we will designate a release in the latter third of the year (Rust 1.29 - 1.31) as Rust 2018. This new “edition” of Rust will be the culmination of feature stabilization throughout the year, and will ship with polished documentation, tooling, and libraries that tie in to those features.

The idea of editions is to signify major steps in Rust’s evolution, where a collection of new features or idioms, taken as a whole, changes the experience of using Rust. They’re a chance, every few years, to take stock of the work we’ve delivered in six-week increments. To tell a bigger story about where Rust is going. And to ship the whole stack as a polished product.

We expect that each edition will have a core theme or focus. Thinking of 1.0 as “Rust 2015”, we have:

* Rust 2015: stability

* Rust 2018: productivity

What will be in Rust 2018?

The roadmap doesn’t say for certain what will ship in Rust 2018, but we have a pretty good idea, and we’ll cover the major suspects below.

Documentation improvements

Part of the goal with the Rust 2018 release is to provide high quality documentation for the full set of new and improved features and the idioms they give rise to. The Rust Programming Language book has been completely re-written over the last 18 months, and will be updated throughout the year as features reach the stable compiler. Rust By Example will likewise undergo a revamp this year. And there are numerous third party books, like Programming Rust, reaching print as well.

Language improvements

The most prominent language work in the pipeline stems from 2017’s ergonomics initiative. Almost all of the accepted RFCs from the initiative are available on nightly today, and will be polished and stabilized over the next several months. Among these productivity improvements are a few “headliners” that will form the backbone of the release:

* Ownership system improvements, including making borrowing more flexible via “non-lexical lifetimes”, improved pattern matching integration, and more.

* Trait system improvements, including the long-awaited impl Trait syntax for dealing with types abstractly.

* Module system improvements, focused on increasing clarity and reducing complexity.

* Generators/async/await: work is rapidly progressing on first-class async programming support.

In addition, we anticipate a few more major features to stabilize prior to the Rust 2018 release, including SIMD, custom allocators, and macros 2.0.

https://blog.rust-lang.org/2018/03/12/roadmap.html

>>880297

1/10

>>881805

Tell me when it gets standardized instead.

>>881810

Can you tell me when C/C++ got standardized?

Kill yourself anti Rust shill

>>881812

Are you retarded? What are C89, C99 and C11?

>>881820

Are you retarded?

>C was originally developed by Dennis Ritchie between 1969 and 1973 at Bell Labs

>In 1989, the C standard was ratified as ANSI X3.159-1989 "Programming Language C".

Now please calculate how long after C's development it got standardized. Then look up how old Rust is. Then kill yourself, anti Rust shill.

Also please tell me why having a standard is important?

>>881822

C was made only for themselves at the beginning. Rust wasn't.

>Also please tell me why having a standard is important?

Learning or even making a 3rd party compiler for an always moving target is a pain. Especially since the stdlib itself isn't standardized I hope they'll cut that nodejs style of "everything must be an out of tree module".

Anyway, stay happy in your faggot circlejerk.

>>881827

>what is mrustc???

https://github.com/thepowersgang/mrustc

>Anyway, stay happy in your faggot circlejerk.

I too would admit defeat with those garbage arguments of yours.

Stay gone, anti Rust shill.

>>881832

>i can't name a single reason why a standard is important

>hahaha.gif

great argument, kid

>>881833

this person here is why Rust is and will be irrelevant for a long time most likely

>>881835

this person here is why /tech/ is and will be irrelevant for a long time most likely

>>882142

Are you trying to imply that Steve Klabnik is trying to imply that the Rust developers invented incremental compilation? Because from what I understand Steve only wrote that in September 2016 he wrote a blog post about incremental compilation.

Can you please quote the specific part where you believe Steve claimed that the Rust developers invented incremental compilation?

I hate these versioning schemes that do nothing but indicate that some time has passed, you could get that information anyway. Version numbers have no meaning anymore.

>>882163

They tell the compiler which words it should consider as keywords. Just because you are an autist and don't like this particular versioning scheme doesn't mean that it's shit.

Also use actual arguments next time.

>>882142

They never said they invented it. They only implemented it in the compiler. Since when are you only allowed to implement technologies you personally invented?

>When Steve Klabnik walks onto the back patio of Fritzl’s Lunch Box in Bushwick to join Tyler, Gregg, and me around a rickety table, it’s as if we already know each other. In a way, some of us do ---the way you can know somebody from the Internet. But Steve also carries himself with welcoming assurance. He’s wearing his typical outfit: a black hoodie and skinny black jeans.

This man just oozes charisma. And he's smart too just check out some of stevers blog posts

>How Dogecoin changed my perspective on cryptocurrency

Almond activating stuff.

I for one will definitely use Rust to fight against capitalism and fascism. Safety First Comrades!!!

>>882162

>>882181

I'm not implying it. I'm saying it outright. You should learn how to read. Rhetoric is real and that's why you elect stupid politicians and buy shitty products.

>Historically, the compiler has compiled your entire project, no matter how little you’ve changed the code.

""historically"" ""historically"" ""historically""

No doubt about the intent.

>>869589 (OP)

https://www.rust-lang.org/en-US/conduct.html

>We are committed to providing a friendly, safe and welcoming environment for all, regardless of level of experience, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other similar characteristic.

>On IRC, please avoid using overtly sexual nicknames or other nicknames that might detract from a friendly, safe and welcoming environment for all.

>Please be kind and courteous. There’s no need to be mean or rude.

>Respect that people have differences of opinion and that every design or implementation choice carries a trade-off and numerous costs. There is seldom a right answer.

>Please keep unstructured critique to a minimum. If you have solid ideas you want to experiment with, make a fork and see how it works.

>We will exclude you from interaction if you insult, demean or harass anyone. That is not welcome behavior. We interpret the term “harassment” as including the definition in the Citizen Code of Conduct; if you have any lack of clarity about what might be included in that concept, please read their definition. In particular, we don’t tolerate behavior that excludes people in socially marginalized groups.

>Private harassment is also unacceptable. No matter who you are, if you feel you have been or are being harassed or made uncomfortable by a community member, please contact one of the channel ops or any of the Rust moderation team immediately. Whether you’re a regular contributor or a newcomer, we care about making this community a safe place for you and we’ve got your back.

>Likewise any spamming, trolling, flaming, baiting or other attention-stealing behavior is not welcome.

http://citizencodeofconduct.org/

>The following behaviors are considered harassment and are unacceptable within our community:

>Violence, threats of violence or violent language directed against another person.

>Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.

>Posting or displaying sexually explicit or violent material.

>Posting or threatening to post other people’s personally identifying information ("doxing").

>Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.

>Inappropriate photography or recording.

>Inappropriate physical contact. You should have someone’s consent before touching them.

>Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.

>Deliberate intimidation, stalking or following (online or in person).

>Advocating for, or encouraging, any of the above behavior.

Sustained disruption of community events, including talks and presentations.

Forbidden hugs when ?

>>882900

>Inappropriate photography or recording

WAT?

What is appropriate then?

Reads like catch-all bullshit.

>>882896

You're a retard. Steve is referring to rustc with "the compiler". Historically, rustc has compiled the entire project.

Kill yourself.

>>882963

Let's discuss within which timeframe using the word "historically" would be appropriate.

If you choose to idolize him, then that's your problem not mine. I'll make fun of the selfimportant manipulative shitbag whenever I fucking please.

>>883039

>i said something retarded but i can't admit it so now i'm going to double down

>>883039

Start with yourself.

>>883228

>i said something retarded but i can't admit it so now i'm going to double down even more

>reddit spacing

Stop shitting up my Rust thread with your autism.

I don't even understand what your problem is. Are you triggered because Steve used the word "historically" and you think it is wrong? Or is it because you misunderstood that Steve was only talking about rustc and not all compilers?

>>883471

>i was only pretending to be retarded

ebin

>>language development falls apart because leads dont agree on "figures of speech", "opinions", "quality control" and "standards" with low level devs who do all the work

>>884063

how come such whiners as these 2 are even possible?

it's such a disgrace. 0/10

>>884063

>[removed]

LOOOL

>>884107

I guess that means he was feeling unwelcome and harassed. Bad job, SJW army!

>>885037

what is your point?

>>885037

are you a brainlet or just trolling?

>>885029

It seems like Steve Klabnik wants people to murder him or something.

>>885042

>>885049

what YOUR point? are YOU a brainlet?

when your brain rusts this is the language

>>869589 (OP)

lol

>>890508

::::::::::::::::::::::::::::::::::::::::::::::::::::::::

WHY::HAS::THIS::THREAD::NOT::BEEN DELETED::YET

::::::::::::::::::::::::::::::::::::::::::::::::::::::::

>>890518

Because it is actually /tech/ related

>>882900

>>890548

Good job, spammer.

>>890549

based mods <3

>offical antifa programming language vs the most white programing langauge other then holy c

>>891924

>>885024

In their delusion they justify violence against innocent people. That's why xey need to be beaten to death.

>>890521

>Because it is actually /tech/ related

Even tho I hate rust he is right.

>>897245

No, he's actually right. The start of knowledge is to call things by their names, and ANTIFA, and those with them on the farther left, are communists. If anyone needs to go back, it's you.

>>>/leftypol/

>>897245

>getting meanings of words correct offends us, right gays?

No nigger, anon is right, and you are wrong. The Antifags bought MSM spin like the dense niggerbrains they are, did violence, and became what they claim to hate. Next up they'll be going to prison for domestic terrorism and buttfucked by turboniggers.:^)

>>897257

>yikes my antifa comrad is getting called out and exposing us for being fascists better slide thread with pointless pedantry

>>897257

U mad? Stallman himself also did that.

>>897298

>>897302

>implying a smug anime character next to a pile of text will automatically make this text 100% not bullshit

>>897708

Ah, a /pol/ JPEG, the one and true source of information.

No.

Rust will prevent all semantic and logical errors

"Error"

unsafe:pajeetvar

"Success"

>>897729

Not reading your conspiracy theory for the millionth time. Especially since all those Twitter accounts are /pol/ false flags anyway. Why don't you keep to watching Nickelodeon shows to unveil cuckold conspiracies?

>>897732

>didn't read can't refute

>>897729 @Jack Dorsey, communist domestic terrorism, Twitter, child rape, human trafficking, TWTR shareholders defrauded

>>897729

In the png the poll about censorship indicates that far more leftists are censored than right wingers looking at the ratio of responses.

>>897738

Not the guy you're replying to but I can't read your picture because I'm over 30.

>>897741

>2+2=5 goy

>leftist math

>>897742

Click on it, it gets bigger.

>>897738

Yes, and the frogs turn gay and it's all a JEWISH and MASON and REPTILIAN conspiracy with CHEMTRAILS and if you (((disagree))) you work for (((them))) wake up sheeple

>>897761

>be dazzled by my handwaving goy

>don't read about @Jack Dorsey, communist domestic terrorism, Twitter, child rape, human trafficking, TWTR shareholders defrauded goy

>>897765

you're mentally ill and ought to get yourself checked

>>897767

>catching me in my (((tricks))) makes you mentally ill

You still haven't addressed >>897729 @Jack Dorsey, communist domestic terrorism, Twitter, child rape, human trafficking, TWTR shareholders defrauded

>>897770

you're a pathetic sad man

>>897776

Before you assume my gender you should address >>897729 @Jack Dorsey, communist domestic terrorism, Twitter, child rape, human trafficking, TWTR shareholders defrauded

>>897780

you drew lines on a collage of anonymous posts. congratulations, mental patient.

>>897781

>didn't read can't refute

>>897787

>>897787

>>897787

>leftist rhetoric in 2018

Stalin would be ashamed of you. @Jack's going to prison.

>>897302

what people mean when they call antifa fascist is they use similar athoritarian attitudes. antifa may not fit the definition completely for facism but the fact they silence other ideas and use violence which is a part of fascism.

>>897791

<Robespierre was a fascist because he silenced the aristocracy and cut their heads off

>>897791

What's really sad is they are unintentional or intentional functionaries of fascists, who use Antifa types ("useful idiots") that are sometimes well intentioned but lack the historical perspective and character to know better. Sad! Case in point >>897792

>>897793

doesnt make the antifa people any less brain dead. people may miss use labels.

>>897795

The Antifa people are most certainly braindead. Look at the chain of "discourse" from >>897787 up. That's what makes them easy to be manipulated and used by fascists. They are the useful idiots of our generation.

>>897788

who the fuck is jack and how is that relevant to rust?

>>897817

Violent commie Rust devs tried to slide >>897729

pic exposing the company they keep. Rust devs promote political violence and censorship, Twitter's complicit, it's the biggest issue in tech and Rust.

>>879253

I don't get it.

Why is there always a thread for this SJW meme lang?

Also, ANTIFA are domestic terrorists.

>>898270

because otherwise there would be no good threads on this board

>>898908

>LARPing

>>898968

Wow, that's pretty close to my ideal C-like language.

>>898975

I was interested it in as a freestanding/OSdev language. I'd seen it recommended for that as an alternative to C in some places, and the zig people list an i386 kernel as one of the projects that's been developed in the language. Found something interesting, though:

>$ ldd /usr/bin/gcc

linux-vdso.so

libm.so

libc.so

ld-linux-x86-64.so

>$ ldd $builddir/zig

linux-vdso.so

libclangFrontend.so

libclangDriver.so

libclangSerialization.so

libclangSema.so

libclangAnalysis.so

libclangAST.so

libclangParse.so

libclangBasic.so

libclangEdit.so

libclangLex.so

libLLVM-6.0.so

libpthread.so.

libxml2.so

libstdc++.so

libm.so

libgcc_s.so

libc.so

libffi.so

libedit.so

libz.so

libdl.so

libncursesw.so

ld-linux-x86-64.so

libicuuc.so

liblzma.so

libicudata.so

Welp. That'd be fun to port. I guess for an embedded system or some kind of autonomous exokernel where you never planned on porting the toolchain for native hosting, it'd be fine. I knew LLVM was part of the bargain, because that's the zig backend, but there's about a dozen other deps. The C++ standard library, ICU, libxml2, etc.

>>898968

Okay, what's the catch, other than the Perl-tier symbol madness syntax?

>>898997

Not until the next age of enlightenment.

>>898994

It's not finalized yet.

Less libraries than with Rust.

Less editor/IDE support.

(All of that is a question of time obviously).

>>898993

Nut sure why this matters much as long as you can cross-compile. Which is a first class goal btw.

>>898997

Not before this stops:

>.gif (2.78 MB)

>>899014

you are the reason of global warming.

Unless https://medium.com/@CBowdon/esr-is-right-about-discovery-cost-and-rusts-stdlib-c7a1839dca8e is fixed, Rust is dead to my eyes. I don't ask Python tier fatness of stdlib, but at least POSIX C.

>>899010

>Less libraries than with Rust.

You mean none?

>>899018

ESR is a retard. Also POSIX is a cancer.

>>898997

Not until people will realize that a language is only as good as its compiler.

>>899024

>ESR is a retard.

I don't care about him, the point still stands.

>Also POSIX is a cancer.

Maybe, but I was talking in term of size/capabilities.

>>899029

Alright I previously haven't read the article because is saw esr in the URL and I remember that he was too retarded to figure out to concatenate two string slices in Rust.

>The distilled point is this: a comprehensive standard library is more practical than a proliferation of community packages.

This is just nonsense. How is it more practical for a module to be in the std instead of being on crates.io (or any other package repo. not that there currently an alternative exists but it is possible to make one)?

>>899038

He explains it in the same fucking article, you retard. Why don't you enable your tripcode so I can filter your stupid uninformed comments, Klabnik?

>>899059

>He explains

Alright the argument why a small std is bad is because community packages are bad and everything std is good because it is blessed by language creators.

This is retarded. Just because something is in the std doesn't make it good nor does it guarantee you that it will not be deprecated.

Python is held up as a good example because the std is large. But protip: Python's std largely sucks.

Anyways I'm done argumenting with some "your a retard XDDDDDDDDDDDDDDDDD sage" faggot.

>>899083

I think you simply didn't read. Unless you're REALLY retarded.

>Alright the argument why a small std is bad is because community packages are bad and everything std is good because it is blessed by language creators.

It's not good, it's consistent, sufficiently documented and almost always maintained unless it's replaced by something that can do the same or more. If you can't get why searching among soyboys' summer projects that will never be maintained to get a basic functionality is bad, you've never programmed.

tl;dr man myfunction (then maybe searching in the SEE ALSO) > searching on a webpage that can't even display something without javascript

>>899098

>your retarded

>soyboy

epic. https://boards.4chan.org/pol/

You still haven't backed up your claim that the std is something magical and community packages are shit.

Python's std still sucks pretty hard even though according to you it should be awesome: http://www.leancrew.com/all-this/2012/04/where-modules-go-to-die/

antisage btw XDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD

>>899098

>rustfag doesn't understand quality control

Color me amazed.

>>899113

>LARPer on /tech/ shits on Rust because >muh SJW while not knowing anything about programming

Color me surprised.

>>899117

>rustfag on /tech/ whining about persecution while thinking rustfags are programmers instead of mlm drones

Color me dazed.

>>899104

Something in the stdlib won't go unmaintained forever without warning. At the very least it won't bitrot, whereas many pre 1.0 Rust libraries are nowadays bitrotten to the core. Not to mention library hunting is more often than not more time consuming than implementing a small subset of what you would need in any monster library, that have API methods for oddly specific usecases mixed with all the shit most people will use.

>>899104

>It's not good

>according to you it should be awesome

Take your pills, faggot.

>>899120

>persecution

please quote me where i expressed that sentiment

>>899136

>pre 1.0

>he calls me a retard

ok

>>899168

>muh SJW

Implies there's something wrong with shitting on you SJWs

>>899182

TIL there's a board for us

>>>/soyboys/

>>899195

Finally I can find some friends to play legos with.

>>899117

>ignores technical point like a faggot

>>899168

>ok

Typical dumb dumb leftist with poor vision can't see the forest for the trees. Anon's point was spot on, and you don't have to look at pre 1.0 libs to see it.

>>899104

>your retarded

>t.niggerbrain

>>899195

>won't die of aids alone

>>899217

Parents at the playground got wise to you trying to befriend their children eh raping lefty?

>>898968

>https://ziglang.org/

>Code of conduct

>Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, inappropriate physical contact, and unwelcome sexual attention.

>Hire

>Our community is 5% black, 6% Latino/a, and over 30% women. We are always striving to build a stronger and more diverse community, and have disbursed over $1M in need-based living expense grants to people from traditionally underrepresented groups in programming over the past four years.

>my sjw meme language is better than yours

Both are trash for faggots.

>>899638

proof that it affects code quality, please.

>>899636

Anti Rust shills are out in full force.

I guess Rust must be pretty good when it can rile you faggots up this much.

Also ROFLMAO @ your arguments:

>muh SJWs

>muh CoC

>muh standard library isn't big enough

/tech/ should be renamed to /g/ TBH.

>>899638

That's a shame. I was hoping that since Python has Pythonistas and Rust has Rustaceans, Zig could have Ziggers. But I guess they'd be too uptight for that. Goddamn blackass ziggers.

Annoucing Rust 1.666

We still havent fixed the most basic problems because we think they are actually features

>anti rust shills are now resorting to spamming inane shit instead of even trying to form a valid argument

wew. rust sure is winning.

>>899900

these aren't writing any code for Zig.

so, not a proof.

I can find examples of shit code written by males as well. In fact, at my work I've seen enough of it.

>>899905

>But I guess they'd be too uptight for that. Goddamn blackass ziggers.

Nobody's stopping us to call it that way anyway.

CoC is not a magical superpower (thanks G-d).

>>899638

I don't see a code of conduct in the zig source code repo or on ziglang.org. Would you mind pointing out where you found that?

>>900032

Probably this https://www.recurse.com/code-of-conduct

I have no idea why he thought it applies to Zig.

Sure, there's a link to this site, but it's only a sponsor.

>>897245

You realize that last time Antifa's monkeyshines actually led to the rise of Hitler don't you?

Just saying you're treading on pretty thin ice. I don't think Antifa even attacks any actual Nazis, they are out there trying to beat up Christian prayer meetings and stuff.

>>898997

soon

https://github.com/BSVino/JaiPrimer/blob/master/JaiPrimer.md

>>900065

>Antifa's monkeyshines actually led to the rise of Hitler don't you?

Surely it wasn't the German higher classes who wished to counter the rise of the Communist party. Surely it wasn't the conservative judge who didn't give the death sentence to Hitler after the Munich putsch (as it was given to left-wing conspirators).

No, it must have been a movement that started in the 70's.

Small announcement from your friendly neighborhood Rust fag: GraalVM can run Rust via LLVM bitcode.

What is GraalVM?

GraalVM is a universal virtual machine for running applications written in JavaScript, Python, Ruby, R, JVM-based languages like Java, Scala, Kotlin, and LLVM-based languages such as C and C++.

GraalVM removes the isolation between programming languages and enables interoperability in a shared runtime. It can run either standalone or in the context of OpenJDK, Node.js, Oracle Database, or MySQL.

https://www.graalvm.org/

>>899038

Because then you don't have to hunt for packages. For instance, when using Flask with Python you need to hunt for a lot of things because Flask is a microframework and does almost everything beyond simple HTTP serving with an extension. Good luck finding the one that's well-maintained and has a good API. This applies to JS and Rust as well; I remember spending hours to find a package giving a specific functionality because there were 10 others that were broken and I had to try each before finding out their shortcomings.

>>900104

>I have no idea why they think this is hip or cool.

>implying golems actually think

>>900028

They are a mark of territory. Of course like a dog pissing somewhere, it doesn't mean they really own the place. Regardless it's only a sponsor. The author seems to be an alumni of whatever kind of school they pretend to be. He himself seems to be a liberal who doesn't talk about politics or social issues. I would rate the zig community as safe for casual professional interaction.

>>900092

But regardless of the language you have to "hunt" for packages. No languages std has everything.

>I remember spending hours to find a package giving a specific functionality because there were 10 others that were broken and I had to try each before finding out their shortcomings.

Sounds like every popular language tbh.

>>900124

This. They don't think. They just get told what to believe in school which is the most successful indoctrination method besides TV.

The jews use our tax money to finance them. What a great democracy in which only 50% votes because of 5% clause and non-voters and the 50% don't even get to decide anything because all parties in the Bundesrat apart from AfD have the exact same ideology and are basically SED split up in parts.

>>900233

*Bundestag

Is this the BILD forums??

>>900150

With a good enough stdlib, you can simply reimplement stuff if you really want to.

>>903023

>Cucklefish

Is it seriously named like that?

>>903023

>>903023

>Cucklefish

okay, so it's actually Chucklefish and not Cucklefish

but nice try

>>903029

you forgot to add soy

>>903030

Soyboy is a retarded meme. I'll stick with cuck.

>>903031

>implying cuck is not a retarded meme

>>903123

>implying it is a meme

>>903174

>.gif

>2.68 MB

go back to reddit

>>900068

Been waiting for years.

>>907339

NOBODY CARES RUSTFAG

>>869673

Imagine being THIS fucking braindead.

>>904105

Yeah man we cant afford fast internet connections from India.

>>899905

>Ziggers

Dirty black ziggers they are, fucking ziggers.

>>900027

The difference is even if they write shit code, which makes them faggots, they don't harp on you about what you should or shouldn't say and do. Nobody but betas want a dumb girl around who thinks she's your mother.

>>900061

Doesn't matter you stupid zigger, it reveals their psychotic politics.

>>900104

>I have no idea why they think this is hip or cool

They don't think, but it doesn't matter. The issue is they can't compete so they

>1. want to le burn it all down

>2. create their own hierarchy

Look at the buttfaggot Steve Klabnick. The only way that greasy queer is getting laid is by lost, true believing, cult adherents.

>>900130

This, totem.

>>903029

I don't think so, you'd see more insecure transniggers and spics.

bump XDDD

Is it worth learning Rust?

>>909920

Good. That means you grew out from the forced meme language.

>>916603

yes

>>916624

I'm still using Rust. I'm just done with /tech/. Too many tech illiterate retards here. I will continue monitoring this thread as long as it's alive though.

>>879332

tits or gtfo

>>881822

>, anti Rust shill.

>, anti Rust shill.

>, anti Rust shill.

I haven't been paying attention to your conversation, but you sure do talk like a child.

Cocks go to hell UwU

>>882900

>There is seldom a right answer.

>we're all wrong, so it's OK

If you trace back the concept of political correctness and this kind of "we're all flawed" speech, you will find it was crafted by the state in order to keep the herd in line. It's basically self-deprecation provided to the masses by the party in control and above it.

The ideals and language is not so much the problem as is the fact that they're being manipulated by powers that are often in complete opposition to those ideals of equality. But since they are packaged in neat little packages for mass consumption and they themselves are out of the reach of the plebs, they're great for manipulating politically and ideologically. It's really terrible what these people are doing to themselves.

>>883251

>Steve

>Steve

>Steve

>Steve

t. Steve

>>869589 (OP)

Apparently there's still no progress with the soundness holes yet:

https://github.com/rust-lang/rust/issues?q=is%3Aissue+is%3Aopen+sort%3Acreated-asc+label%3A"I-unsound+💥"

But now they added an emoji to the URL. That must be great.

>>917177

I need to manually URL-encode these parts to make it a parseable URL:

https://github.com/rust-lang/rust/issues?q=is%3Aissue+is%3Aopen+sort%3Acreated-asc+label%3A%22I-unsound+%F0%9F%92%A5%22

>>909920

>not shilling rust anymore

>>917178

>>917177

>>917152

>>917149

>>917138

>>917130

>>917128

>>916912

>>916603

>>915267

<samefag bumps the shill thread another 10 times

>>917235

Half of those posts are sages.

You anti Rust shills really are the most pathetic of all shills. Good thing that you are mostly contained on /tech/.

Steve you faggot what do you think about impl Trait in argument position? I didn't know it existed or that it was merged into stable. Seems to be nice for things like

fn nigger(_target: impl AsRef<Path>, _dest: impl AsRef<Path>) {}

fn main() {
    nigger("aaa", Path::new("bbb"));
}

>>918023

Scratch that it's shit

>>918023

The community is upset.

https://www.reddit.com/r/rust/comments/8l0ywr/rfc_undo_universal_impl_trait/

Announcing Rust 1.25

you have sign "diversity license" or you are racist

>>900150

The argument wasn't for containing everything, it's about containing stuff regularly used by developers.

>>918023

>>918191

>>918193

>>918207

>>918321

this is all the rustfag once again bumping his shill thread talking to himself.

https://blog.rust-lang.org/2018/05/15/Rust-turns-three.html

Rust turns three

>Rust is a people-centric, consensus-driven project. Some of the most exciting developments over the last year have to do with how the project itself has grown, and how its processes have scaled.

>The official teams that oversee the project doubled in size in the last year; there are now over a hundred individuals associated with one or more of the teams. To accommodate this scale, the team structure itself has evolved. We have top-level teams covering the language, library ecosystem, developer tooling, documentation, community, and project operations. Nested within these are dozens of subteams and working groups focused on specific topics.

>Rust is now used in a huge variety of companies, including both newcomers and big names like Google, Facebook, Twitter, Dropbox, Microsoft, Red Hat, npm and, of course, Mozilla; it’s also in the top 15 languages this year on GitHub. As a byproduct, more and more developers are being paid to contribute back to Rust, many of them full time. As of today, Mozilla employees make up only 11% of the official Rust teams, and just under half of the total number of people paid to work on Rust. (You can read detailed whitepapers about putting Rust into production here.)

>Rust’s growth continues to accelerate at a staggering rate. It has been voted the Most Loved Language on StackOverflow for all three years since it shipped. Its community has never been healthier or more welcoming. If you’re curious about using or contributing to Rust, there’s never been a better time to get involved.

>Happy 3rd birthday, Rust.

>>918355

bump XDDDDDDDDDDDDDDDDDDDDDDDD

>>918355

Nice way to get guaranteed bumps, LARPnik.

Don't leave us, Klabnikposter. I want to continue laughing at you and your shit language.

Funny how all the C cucks are posting in this thread. It's like they know their lang is shit.

>>922115

>C is easy to use

http://port70.net/~nsz/c/c99/n1256.html#J.2

>>922122

C is the only fast language that exists, everything else is bloated and for pajeets

>>922125

>>C is easy to use

>http://port70.net/~nsz/c/c99/n1256.html#J.2

I didn't say anything aboust the speed of C.

https://blog.mozilla.org/nnethercote/2018/06/05/how-to-speed-up-the-rust-compiler-some-more-in-2018/

Daily breakthroughs! How exciting!

>>925256

>blog is 'how to speed it up in 2018'

>not 'how to speed it up'

I think it's crossed into scam territory now, like a crowd-funded video game that plans around never actually having a finished product and just making scheduled blog posts forever. It's been three years of these "speed up" updates and it's still not even close to acceptable for real development. Looks like the people who said the design wouldn't scale were right, it's fundamentally fucked.

>>925265

>hurr durr rust sucks XDDDDDDDDDD i have no idea about rustc nor software development LARP LARP

ok kid

Ada is better.

>>925272

proof?

>>925270

I don't know anything about compilers or this particular issue. In fact, I like Rust and would like to see it grow, but somehow you managed to kill all credibility you had by sperging and overreacting in that manner.

You are extremely immature.

>>925309

>xDDDDD i actually hate rust now because of you :DDDDDDDD LARP LARP

You are extremely retarded if you expect me to believe you.

https://github.com/rust-lang/rust/pull/51580

>async/await

>This PR implements async/await syntax for async fn in Rust 2015 and async closures and async blocks in Rust 2018 (tracking issue: #50547). Limitations: non-move async closures with arguments are currently not supported, nor are async fn with multiple different input lifetimes. These limitations are not fundamental and will be removed in the future, however I'd like to go ahead and get this PR merged so we can start experimenting with this in combination with futures 0.3.

http://smallcultfollowing.com/babysteps/blog/2018/06/15/mir-based-borrow-check-nll-status-update/

>MIR-based borrow check (NLL) status update

>NLL is in a “feature complete” state on Nightly.

>We are doing a focused push on diagnostics and performance, primarily.

>Even once it ships, we can expect further improvements in the future, as we bring in the Polonius analysis.

https://github.com/rust-lang/rust/blob/master/RELEASES.md

>Version 1.27.0 (2018-06-21)

>The dyn syntax is now available. This syntax is equivalent to the bare Trait syntax, and should make it clearer when being used in tandem with impl Trait. Since it is equivalent to the following syntax: &Trait == &dyn Trait, &mut Trait == &mut dyn Trait, and Box<Trait> == Box<dyn Trait>.

>The #[must_use] attribute can now also be used on functions as well as types. It provides a lint that by default warns users when the value returned by a function has not been used.

>SIMD (Single Instruction Multiple Data) on x86/x86_64 is now stable. This includes arch::x86 & arch::x86_64 modules which contain SIMD intrinsics, a new macro called is_x86_feature_detected!, the #[target_feature(enable="")] attribute, and adding target_feature = "" to the cfg attribute.

>>925274

Just look at this list of companies using Ada in 2018:

>>925274

For starters, Ada is based on a set of well defined principles and requirements. Later updates to the language are verified against these principles as well.

They just keep adding stuff to Rust, I doubt there is much planning behind it. I think the version history proves my point.

Furthermore Rust ignores the readability aspect by having syntax "inspired" by C.

>>931239

>They just keep adding stuff to Rust, I doubt there is much planning behind it.

What updates to Rust go against Rust's principles? Do you even know what an RFC is?

>I think the version history proves my point.

How so?

>Furthermore Rust ignores the readability aspect by having syntax "inspired" by C.

>muh syntax

Please specify how Rust's syntax is unreadable?

I suspect that you are a retarded nodev. You most likely don't know Ada nor Rust yet still shitpost about it. Kill yourself.

>>931242

>24 versions of a 1.0 language in 3 years is fine.

Just admit your toy language is still in beta.

>muh syntax

Shortest I can give you is that any translation that needs to be done from syntax to meaning is cognitive load that hinders readability.

Poor readability hinders debugging and maintenance.

Using curly brackets is the most obvious sin. Then using fn for both functions and procedures is questionable at best.

More gold from the Faq.

> Why doesn't Rust have exceptions?

>Exceptions complicate understanding of control-flow, they express validity/invalidity outside of the type system, and they interoperate poorly with multithreaded code (a major focus of Rust).

>Rust prefers a type-based approach to error handling, which is covered at length in the book. This fits more nicely with Rust’s control flow, concurrency, and everything else.

Guess which language has both an extensive type system, concurrency, "and" exceptions...

>>931255

>>24 versions of a 1.0 language in 3 years is fine.

>Just admit your toy language is still in beta.

ok

>Shortest I can give you is that any translation that needs to be done from syntax to meaning is cognitive load that hinders readability.

>Poor readability hinders debugging and maintenance.

I love how you haven't actually specified how it is unreadable.

>Using curly brackets is the most obvious sin. Then using fn for both functions and procedures is questionable at best.

Are you actually retarded?

>Guess which language has both an extensive type system, concurrency, "and" exceptions...

Is it also memory and thread safe all without GC?

Yeah seems like I was right. You can't go into specifics because you don't know anything about Rust. All you can do is spout the same bullshit that /tech/ has been for years now.

Can you explain how updating a language is bad?

Can you explain what exactly is bad about the syntax without stating completely subjective shit like curly braces and how functions are identified?

Can you explain what is wrong with the FAQ entry about why Rust doesn't have exceptions?

>>931257

To continue, from the Rust book on functions, (first version though)

>As we mentioned before, fn says "this is a function"

Except you know, when your function doesn't return a value, it maybe shouldn't be called a function...

Ada hasn't got any GC, or to be more specific, no implementation supports GC. Pretty memory safe unless you choose to do your own allocation and deallocation.

>All those Ad-homs

Nice arguments. Please explain how staring at curly brackets and using fn to mean function (and procedures as above) is good for readability.

>Can you explain what is wrong with the FAQ entry about why Rust doesn't have exceptions?

It claims exceptions and concurrency can't go together, Ada does this however.

>Can you explain how updating a language is bad?

Updating your beta is fine, don't pretend it is done. Pretending it is done constrains your freedom of design for starters.

>Can you explain what exactly is bad about the syntax without stating subjective things.

Well, I suppose you could just claim everything I say is subjective and win your argument.

To add to the retardation that is fn procedures, am I correct in thinking you can't distinguish between in and out parameters? Or am I missing something.

As for the type system, so far there doesn't seem to be any type system. Top kek.

Maybe I'm mistaken, but how are you going to catch any logic errors, like adding apples to oranges, if your type system is basically nothing more than unsigned and signed numbers of various sizes?

>>931270

>still no specifics

>Except you know, when your function doesn't return a value, it maybe shouldn't be called a function...

lol

>Please explain how staring at curly brackets and using fn to mean function (and procedures as above) is good for readability.

lol. Look at literally any software. It most likely is written a language that has curly braces.

>It claims exceptions and concurrency can't go together

<have a threadpool

<execute a function in it

<function throws an exception

<threadpool is fucked

sounds like fun

>Updating your beta is fine, don't pretend it is done.

ok

>Well, I suppose you could just claim everything I say is subjective and win your argument.

>everything

no

>As for the type system, so far there doesn't seem to be any type system. Top kek.

ok

>Maybe I'm mistaken, but how are you going to catch any logic errors, like adding apples to oranges, if your type system is basically nothing more than unsigned and signed numbers of various sizes?

You are mistaken.

Just stop, dude. You just admitted that you don't know anything about Rust.

>Don't know anything

I do know some things. But maybe you can help me out fill in the gaps. Lets start with the basics.

Can Rust do the following?

declare
type apple is new  Integer; --using natural instead of integer would make more sense
type orange is new Integer; --But I don't want to confuse any "crustacians"
A: apple := 1;
O: orange := 2;
begin
A := A+O; --This won't compile.  
end;

>>931300

>I do know some things.

apparently not

https://play.rust-lang.org/?gist=0dca332428ef91951f8879a864ce6ce6

>>931303

>Workaround by using structs

Top jej.

>>931306

>he needs special syntax (aka bloat) for basic stuff like this

wew lad

>>931308

>bloat

>Catching errors at compile time is now bloat

>A language having to use structs to achieve the same thing is fine though

This is your brain on rust

>>931467

Why would you introduce special syntax for something that can be done with existing means?

Can you explain this? This is a rhetorical question. Of course you can't because you are a LARPer.

>>931469

Because special syntax can be used to communicate intent to people reading the code.

Furthermore, time spend reading code often larger than writing said code. So clear communication becomes even more important, especially further down the road when new people get involved.

>can be done with existing means.

And a saw can be used to drive a nail in a piece of wood.

Your suggested solution involving structs gets even more ugly and bloated once you start nesting them.

>Even more adhoms

Great arguments once again.

Please explain how using structs instead of scalar types is not bloat.

>>931474

>Because special syntax can be used to communicate intent to people reading the code.

The more syntax a language has the harder it is to learn it. Just take a look at C++.

>And a saw can be used to drive a nail in a piece of wood.

That analogy sucks. Try again.

>Please explain how using structs instead of scalar types is not bloat.

struct Apple(i32) will compile down to a i32. Absolutely no bloat.

>muh ad hominems

Well stop spouting nonsense about stuff you don't know anything about then.

>>931479

Complex languages are harder to learn. Having good syntax makes understanding code and learning the language easier.

>That analogy sucks. Try again.

It is a perfect analogy, your goal can be achieved, but it is hardly elegant.

I wanted to increase the apple count by one, which shouldn't be a problem I think.

But it complains that add cannot be applied to apple.

I hope there is an elegant solution to this in Rust.

https://play.rust-lang.org/?gist=4bb861e8c78cf7af75b918a837042968&version=stable&mode=debug

>>931485

You are trying to add an i32 to an Apple. Why do you think this should be allowed?

Her let me quote you: >>931270

>Maybe I'm mistaken, but how are you going to catch any logic errors, like adding apples to oranges, if your type system is basically nothing more than unsigned and signed numbers of various sizes?

>>931486

Well, I understand why I get that error, but what is your solution? I sure hope it doesn't involve too much bloat.

Of course we wouldn't be having this problem in Rust if we could type scalars.

Thanks for the quote, it helps prove this point.

declare
type apple is new  Integer; 
type orange is new Integer; 
A: apple := 1;
O: orange := 2;
begin
   A := A + 1; --Add an apple
   A := A - 1; --eat an apple
   A := A * 2; --Jesus visits
end;

>>931512

There are multiple solutions. Here is one: https://play.rust-lang.org/?gist=501f4296eca881c70c90333dbcd90c31

>>931513

I expected something like that, but now you end up referring to the first element of your struct all the time. You might call this bloat.

I think other solutions would involve defining the operators to work on your struct, or maybe defining functions to modify the amount of apples in your struct.

In any case, you could argue that the very simple requirement of preventing adding apples to oranges leads to somewhat convoluted solutions.

>>899015

Burn nigger burn.

borrow checker BTFO

https://github.com/actix/actix-web/issues/289

https://old.reddit.com/r/rust/comments/8s7gei/unsafe_rust_in_actixweb_other_libraries/

>>932219

his gf looks kinda young tbh

Why aren't the people butthurt about Rust flooding this thread? It's the ideal meme vector against Rust and the only guy who responds to me is Steve Klabnik. Seems like /tech/ only consists of LARPers. I'm not surprised.

>>932333

gentleman's agreement

>>932212

>>932219

Faggot works at M$ what do you expect? It's in their DNA to write shitty unsafe code.