Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Shipping Rust code in Firefox

hacks.mozilla.org

Post reply on HN
Print view View original

181–190 of 197 posts

Re: Shipping Rust code in Firefox

#181

Post by masklinn »

Manishearth wrote: post #151
themihai wrote: post #134

Earlier quoted context omitted.

You are right about the compiler changes but even so you can't compare 1-2 compiler BK with Rust which has language changes as well. Compiler changes are the norm in Rust. >> The parts of the Rust standard library that are marked stable have remained completely backwards compatible, in both interface and implementation. This looks like a breaking change on a stable API. Am I wrong? https://github.com/rust-lang/rust/p…

> Compiler changes are the norm in Rust. Compiler changes are the norm everywhere? I'm not sure what you're trying to say here. > This looks like a breaking change on a stable API. Am I wrong? Yes and no. Rust's policy on breaking changes is that changes that can be fixed by properly qualifying an implicit path are not breaking. Otherwise, adding any method to anything would be a breaking change. In this case, you ca…

> Go doesn't have this issue

Steve has pointed out that go did have this issue as it has a limited level of auto-deref, which it has changed in the past: implementations performed two levels of auto-deref when executing methods when the spec only requires one, the implementations were changed to only allow a single auto-deref: https://golang.org/doc/go1.4#methodonpointertopointer

Re: Shipping Rust code in Firefox

#183

Post by Manishearth »

masklinn wrote: post #181
Manishearth wrote: post #151

Earlier quoted context omitted.

> Compiler changes are the norm in Rust. Compiler changes are the norm everywhere? I'm not sure what you're trying to say here. > This looks like a breaking change on a stable API. Am I wrong? Yes and no. Rust's policy on breaking changes is that changes that can be fixed by properly qualifying an implicit path are not breaking. Otherwise, adding any method to anything would be a breaking change. In this case, you ca…

> Go doesn't have this issue Steve has pointed out that go did have this issue as it has a limited level of auto-deref, which it has changed in the past: implementations performed two levels of auto-deref when executing methods when the spec only requires one, the implementations were changed to only allow a single auto-deref: https://golang.org/doc/go1.4#methodonpointertopointer

Right. However, as I mentioned in the edit, you can still be careful about avoiding breaking changes through inheritance and autoderef in the evolution of Go's stdlib. It forbids very specific types of methods from being added, and if you avoid that, you can continue to add methods as if nothing is wrong.

Rust (and C++, because SFINAE, and many other languages), on the other hand, technically has a breaking change each time any method is added to any public type in the stdlib. It's always possible that the client lib was using a trait method of the same name, and now has to fully qualify the method call.

Re: Shipping Rust code in Firefox

#184

Post by comzeradd »

snuxoll wrote: post #63
steveklabnik wrote: post #62

Earlier quoted context omitted.

Ah, bummer. How long between Fedora releases?

6 months, all that needs to get in is a proposal (first alpha is a month away so there's plenty of time to flesh it out). We can still package rustc without needing a change, but cargo would be delayed if there isn't a proposal on the wiki before the end of day.

There is already a bug tracking this effort for Fedora https://bugzilla.redhat.com/show_bug.cgi?id=915043

Also a few unofficial repos for rust/cargo on Copr https://copr.fedorainfracloud.org/coprs/fulltext/?fulltext=r...

Re: Shipping Rust code in Firefox

#186

Post by [deleted] »

snuxoll wrote: post #63
steveklabnik wrote: post #62

Earlier quoted context omitted.

Ah, bummer. How long between Fedora releases?

6 months, all that needs to get in is a proposal (first alpha is a month away so there's plenty of time to flesh it out). We can still package rustc without needing a change, but cargo would be delayed if there isn't a proposal on the wiki before the end of day.

[deleted]

Re: Shipping Rust code in Firefox

#187

Post by fnord123 »

comzeradd wrote: post #184
snuxoll wrote: post #63

Earlier quoted context omitted.

6 months, all that needs to get in is a proposal (first alpha is a month away so there's plenty of time to flesh it out). We can still package rustc without needing a change, but cargo would be delayed if there isn't a proposal on the wiki before the end of day.

There is already a bug tracking this effort for Fedora https://bugzilla.redhat.com/show_bug.cgi?id=915043 Also a few unofficial repos for rust/cargo on Copr https://copr.fedorainfracloud.org/coprs/fulltext/?fulltext=r...

Will Fedora ever rename/relogo Copr? Surely it was a joke to use the Greek word for faeces (κόπρο) and a logo of a side-on view of a sphincter pushing out a fresh coil.

Re: Shipping Rust code in Firefox

#188

Post by Noseshine »

smt88 wrote: post #22
maxerickson wrote: post #15

Earlier quoted context omitted.

The headline is nerdview. http://languagelog.ldc.upenn.edu/nll/?p=26094

There is a whole article that explains the headline. The headline can't include 100% of background.

But a headline can be correct or incorrect. That they changed the headline shows a lot of users thought it was incorrect.

Re: Shipping Rust code in Firefox

#189

Post by Noseshine »

hyperpape wrote: post #86
maxerickson wrote: post #54

Earlier quoted context omitted.

Sure, it wasn't egregious, but I think the insider perspective idea has lots of explanatory power when it comes to the confusion Noseshine expressed and the surprise wyager responded to the confusion with.

Well, obviously we can disagree and I could be wrong, but I think Noseshine's response was a "man bites dog" situation. After thinking about it, I'd still expect the intended audience to see it.

What does "man bites dog situation" mean? Looking at the Wikipedia explanation for the phrase in the context of journalism it supports my question about the title: Extreme and rare events are more likely to be reported. Obviously shipping "Rust code" is much less noteworthy than "shipping Rust" would be.

Re: Shipping Rust code in Firefox

#190

Post by merandacurtis »

whateveracct wrote: post #96
lovelettr wrote: post #91

Earlier quoted context omitted.

Where is the feature in GitHub that would show the languages used in a repository? That would be useful here regarding this comment. (Note I have no doubt you are right. It would just be a useful metric.)

Did they just..get rid of it? I can't find it either.

Me neither
Post reply on HN