Re:Making Rust as Fast as Go
by steveklabnik on Monday May 04, 2020 @12:18PM
(#23069880)
(We already do do this in some cases; these crates are authored by "The Rust Project Developers". For example, the regex crate is one of these.)
Re:Making Rust as Fast as Go
by jfkebwjsbx on Monday May 04, 2020 @12:55PM
(#23070408)
Yeah, but that makes them third-party already for many orgs' policies, even if they come from the same set of developers.
As soon as you have to add a crate, you are in for extra review and pain.
Re:Making Rust as Fast as Go
by steveklabnik on Monday May 04, 2020 @01:02PM
(#23070513)
I don't understand, wasn't
> it was that the core team consider releasing "core" language features like Unicode support as first-party crates
what you were asking for?
Re:Making Rust as Fast as Go
by arcticbull on Monday May 04, 2020 @02:01PM
(#23071229)
I think that's what I was asking for, but I'm not the person you were replying to ^_^, they were taking a more hard-line stance that it should be part of libstd.
Side-note I really appreciate all the work you folks are doing. Rust has changed the way I write software even when I'm not writing Rust, which is about the highest praise I can offer.
I'd love to pitch in.
Re:Making Rust as Fast as Go
by steveklabnik on Monday May 04, 2020 @02:57PM
(#23071885)
Whoops, how embarrassing for me!
Thanks :)
... how would you like to pitch in? I can point you to the right people. We're always happy to have more help.
Again, my recommendation wasn't that, it was that the core team consider releasing "core" language features like Unicode support as first-party crates when they don't make sense as part of 'stdlib' not that I think they will. Feels weird to me that I have to rely on the goodwill of third parties to provide core language functionality like complete string handling.