TWiR quote of the week

[RDambrosio016]

From a zulip thread i started by Lokathor

Note: function pointers are not always aligned, though some platforms may have them be aligned

Anyway: the standard library docs say "check the nomicon"
then the nomicon says "here is some advice and ultimately we don't know, maybe check UCG"
then UCG says "ultimately we don't know it's probably like this but there's no RFC yet"
then Ralf says "probably it should be allowed if the layout matches".

I found this pretty funny and sad.

Not sure whether to include the first sentence or not, you decide

[jameseb7]

@H2CO3

In Rust, soundness is never just a convention.

From @H2CO3 in Rationale behind Fn, FnMut and FnOnce design

[lain-dono]

From the russian telegram chat room Telegram: Contact @rust_offtopic

Original:

Кстати я знаю чем занимается борроу чекер
Чекает не свихнулся ли ты еще

In English:

By the way i know what borrow checker does
Checks to see if you're still crazy

[Cerberuser]

Isn't the translation inverted? "Не свихнулся ли ещё" literally means "isn't crazy yet".

[lain-dono]

Both are correct in their own way. The craziness is UB.

[mark-i-m]

Edition!

From: Rust 2021 Edition - YouTube

[amanjeev]

Deirdre Connolly¹

A huge of Rust is "you're holding it wrong" is considered a language bug.

[macronaut]

Hot take: Rust isn't as hard as it's detractors think it is, and it isn't as easy as we want it to be. But I think we have a better chance of becoming easier to use than easier use languages becoming lower level without compromises.

Link

[Mokuz]

I think Rust being difficult is like saying you had good parents because they let you play with knives. Rust may seem hard at first but borrowck is just looking after you.

To elaborate writing a fast and memory safe multi-threaded webserver is easy in Rust; if it compiles it works, but difficult in C since while it may be easier to get it to compile it might not work correctly.

[mmmmib]

the strains of the project have hurt a lot of people over the years and I think maybe the only path to recovery involves getting some distance from it.

Graydon Hoare on Twitter

[zeroexcuses]

@Hyeonu

unsafe {} literally means "shut up compiler I know what I'm doing and this code doesn't have any UB". In this case you've lied to the compiler, there's no guarantee that the compiler gives you meaningful result back.

Why the code compiles?

unsafe {} literally means "shut up compiler I know what I'm doing and this code doesn't have any UB". In this case you've lied to the compiler, there's no guarantee that the compiler gives you meaningful result back.

[zeroexcuses]

@Michael-F-Bryan

FP languages are often completely immutable so you'll fall into this pattern naturally. It's kinda hard to create a half-initialized thing and populate it later when you aren't allowed to mutate anything.

Common newbie mistakes or bad practices

I think it also depends on your background or coding style. FP languages are often completely immutable so you'll fall into this pattern naturally. It's kinda hard to create a half-initialized thing and populate it later when you aren't allowed to mutate anything. On the other hand, OO languages are much happier to let you initialize an object after it has been constructed, especially because object references can be null by default and they have no qualms about mutability... You could argue t…

[EvanCarroll]

He devoted his talk to not trolling,

"That's enough about languages that suck, let's talk about C++" - Miguel Young de la Sota speaking on Rust's handling of Pin before talking about C++ at RustConf 2021

[zeroexcuses]

@ZiCog

Politic: Before we had written a line of code our former employer threatened to sue us thinking we had stolen the code we wrote for them before they went bust. We had not. I thought it would be prudent to implement the similar functionality we needed in a different language, just in case. So what was JS and node.js became Rust.

https://users.rust-lang.org/t/common-newbie-mistakes-or-bad-practices/64821/46

[ZiCog]

It's nice to be quoted on TWiR.

But is that intended to be an example of a newbie mistake or bad practice? Or the opposite.

[zeroexcuses]

@ZiCog

But is that intended to be an example of a newbie mistake or bad practice? Or the opposite.

I got a chuckle out of the following visualization:

ZiCog's former employer: They copy pasted our code.
ZiCog: They used JS. We use Rust.
Judge: Case closed.

EDIT: I am not a lawyer. The above is not legal advice. If you are in ZiCog's situation, consult a lawyer.

[ZiCog]

Allmost right.

Except they accused us of having run away with the code for an entire project, which we were picking up from an existing customer. And of not delivering it to them, after we had and they had not paid us or the office rent for months.

I was inspired by the story of Compaq and others clean room reverse engineering the IBM PC BIOS so that they could make PC clones without stealing the original BIOS code. So I was looking to start over with a new language, I had only then discovered Rust and soon decided to bet the farm on it. It's been working very well.

"Case closed". Well, we have not heard back from them... yet.

Luckily my partner's girl friend is a well qualified commercial lawyer

[pickfire]

Rust maybe “multi-paradigm general-purpose programming language” but it's also incredibly opinionated and tries very hard to stir you toward “great APIs” (good APIs are easy to use, great APIs are hard to abuse).

I think just maybe not "incredible opinionated" but the last words seemed nice.

Common newbie mistakes or bad practices

I'm not sure if this belongs here or in some other place, but if novice in question is not a total novice then probably the most common mistake they do is an attempt to write JavaScript in Rust or Python in Rust or some other language in Rust. Rust is usually presented as “multi-paradigm general-purpose programming language” which somehow convinces people who know some other mainstream language that they should be able to just write code in Java or C# and then, somehow, mechanically translate …

[Yandros]

@quinedot

The signature of your function is your contract with not only the compiler, but also users of your function.

Succintly put , this is sometimes overlooked.

[bes]

RustConf 2021: - Compile-Time Social Coordination by Zac Burns

Do you want to know what was harder than learning lifetimes? Learning the same lessons through twenty years of making preventable mistakes.

Perfect.