Re: Rust as build requirement was Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

Replying to a couple messages at once. On 12/14/15 2:19 PM, Mike Hoye wrote: On 2015-12-14 4:06 PM, Justin Dolske wrote: On 12/14/15 2:51 AM, Ted Mielczarek wrote: [...]Obviously this isn't something we like to see, but we shouldn't let the support of non-Tier 1 platforms guide our decision

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On Sun, Dec 13, 2015, at 09:27 PM, Nicholas Nethercote wrote: > On Sun, Dec 13, 2015 at 11:28 AM, Bobby Holley > wrote: > >> > >> I've been wondering about this. There's a big difference between (a) > >> permitting Rust components (while still allowing fallback C++ > >>

Re: Rust as build requirement was Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On Mon, Dec 14, 2015 at 6:58 PM, Cameron Kaiser wrote: > Replying to a couple messages at once. > > On 12/14/15 2:19 PM, Mike Hoye wrote: > >> On 2015-12-14 4:06 PM, Justin Dolske wrote: >> >>> On 12/14/15 2:51 AM, Ted Mielczarek wrote: >>> >>> [...]Obviously this isn't

Re: Rust as build requirement was Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

Well, this wouldn't be the first time that we are not as clear communicating our intents as we thought or should. Sorry about that. Thanks for getting in touch with the OS/2 maintainer. We definitely need to spread the word asap. I hope that Rust can be ported to OS/2 and other Tier-3 platforms

Re: Rust as build requirement was Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On 12/14/15 7:36 PM, Gregory Szorc wrote: On Mon, Dec 14, 2015 at 6:58 PM, Cameron Kaiser wrote: That said, I kind of object to the fact that no one brought this up until I noticed it in passing, and the work to get Rust up on a tier-3 platform -- a language that

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On Sun, Dec 13, 2015 at 10:50 AM, Nicholas Nethercote wrote: > On Sun, Dec 13, 2015 at 9:17 AM, Cameron Kaiser wrote: >> >> This would essentially mandate, then, that Gecko can only be built on >> platforms with a Rust toolchain. That may be

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On Sat, Dec 12, 2015 at 5:17 PM, Cameron Kaiser wrote: > This would essentially mandate, then, that Gecko can only be built on > platforms with a Rust toolchain. That may be desirable, but it would > probably bust some of the obscure Tier-3 platforms and it would definitely

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On 2015-12-14 4:06 PM, Justin Dolske wrote: On 12/14/15 2:51 AM, Ted Mielczarek wrote: [...]Obviously this isn't something we like to see, but we shouldn't let the support of non-Tier 1 platforms guide our decision making to that extent. Enabling Rust components in Gecko is important work, and

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On 12/14/15 2:51 AM, Ted Mielczarek wrote: [...]Obviously this isn't something we like to see, but we shouldn't let the support of non-Tier 1 platforms guide our decision making to that extent. Enabling Rust components in Gecko is important work, and outweighs the value of supporting Firefox on

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On Sun, Dec 13, 2015 at 9:17 AM, Cameron Kaiser wrote: > > This would essentially mandate, then, that Gecko can only be built on > platforms with a Rust toolchain. That may be desirable, but it would > probably bust some of the obscure Tier-3 platforms and it would

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On Sun, Dec 13, 2015 at 11:28 AM, Bobby Holley wrote: >> >> I've been wondering about this. There's a big difference between (a) >> permitting Rust components (while still allowing fallback C++ >> equivalents) and (b) mandating Rust components. > > I don't know why we would

Re: Rust as build requirement was Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On 12/13/15 12:50 AM, Nicholas Nethercote wrote: On Sun, Dec 13, 2015 at 9:17 AM, Cameron Kaiser wrote: This would essentially mandate, then, that Gecko can only be built on platforms with a Rust toolchain. That may be desirable, but it would probably bust some of the

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On Sun, Dec 13, 2015 at 3:50 AM, Nicholas Nethercote wrote: > On Sun, Dec 13, 2015 at 9:17 AM, Cameron Kaiser > wrote: > > > > This would essentially mandate, then, that Gecko can only be built on > > platforms with a Rust toolchain. That may be

Re: Rust as build requirement was Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

> On the other hand, in that same thread, metajack said, "The current plan is > to have Rust (in the form of rust-url replacing nsUrlParser) riding the > trains later this quarter." And indeed, Rust is now riding the trains with the moov parser. It's not required for the build yet, but Nightly

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On Sun, Dec 13, 2015 at 2:28 PM, Bobby Holley wrote: > I don't know why we would allow there to be a long gap between (a) and (b). > Maintaining/supporting two sets of the same code is costly. So if we get > the rust code working and shipping on all platforms, I can't

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On Sun, Dec 13, 2015 at 6:27 PM, Nicholas Nethercote wrote: > On Sun, Dec 13, 2015 at 11:28 AM, Bobby Holley > wrote: > >> > >> I've been wondering about this. There's a big difference between (a) > >> permitting Rust components (while still

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On 12/4/15 3:53 AM, Henri Sivonen wrote: Hi, I have written a proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust: https://docs.google.com/document/d/13GCbdvKi83a77ZcKOxaEteXp1SOGZ_9Fmztb9iX22v0/edit [...] Furthermore, I think the rewrite should be in Rust, because a)

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On Sat, Dec 12, 2015 at 5:17 PM, Cameron Kaiser wrote: > On 12/4/15 3:53 AM, Henri Sivonen wrote: > >> Hi, >> >> I have written a proposal to a) rewrite Gecko's encoding converters >> and b) to do it in Rust: >> >>

Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

Hi, I have written a proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust: https://docs.google.com/document/d/13GCbdvKi83a77ZcKOxaEteXp1SOGZ_9Fmztb9iX22v0/edit I'd appreciate comments--especially from the owners of the uconv module and from people who have worked on

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On Fri, Dec 4, 2015 at 5:54 PM, Henri Sivonen wrote: > On Fri, Dec 4, 2015 at 3:18 PM, Ted Mielczarek wrote: >> 2) Instead of a clean-room implementation, would it be possible to fix >> the problems you see with rust-encoding so that it's suitable for

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/04/2015 04:54 PM, Henri Sivonen wrote: > On Fri, Dec 4, 2015 at 3:18 PM, Ted Mielczarek > wrote: >> 1) What does Servo do, just use rust-encoding directly? > > That is my understanding, but it would be good if a Servo >

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On Fri, Dec 4, 2015 at 3:18 PM, Ted Mielczarek wrote: > 1) What does Servo do, just use rust-encoding directly? That is my understanding, but it would be good if a Servo developer could confirm. > 2) Instead of a clean-room implementation, would it be possible to fix > the

Re: Proposal to a) rewrite Gecko's encoding converters and b) to do it in Rust

On Fri, Dec 4, 2015, at 06:53 AM, Henri Sivonen wrote: > Hi, > > I have written a proposal to a) rewrite Gecko's encoding converters > and b) to do it in Rust: > https://docs.google.com/document/d/13GCbdvKi83a77ZcKOxaEteXp1SOGZ_9Fmztb9iX22v0/edit > > I'd appreciate comments--especially from the