Conversation

For every Rust project, there must be a C project. Maintain the rewrite-in-C agenda.

3
0
0

@eoaiuastwg
rewrite-in-C sounds good but I don't think we should replicate Rust's attitude towards dependencies.

How about one big beau^W library called libexrust-common that has everything from memchr to logging to json serialization?

1
0
0

@koakuma @eoaiuastwg mrustc exists, though it's more for bootstrapping purposes ("i have a C++ compiler (that i got from somewhere), i need a rust compiler")

0
0
0

@5225225 @wolf480pl @eoaiuastwg yeah imo out of the options the “lots of small libraries that do one thing well” approach is probably the best one. C practically doesn’t let you do that so you get copy-pasted outdated copies of the same code and big kitchensink libraries instead

1
0
0

@charlotte
it would be the best approach if all these small libraries had stable ABIs, no regressions, and were developed by the same team, and you were good friends with their release manager
@eoaiuastwg @5225225

1
0
0

@wolf480pl @eoaiuastwg @5225225 see the “practically doesn’t let you do that” part

1
0
1

@charlotte @eoaiuastwg @wolf480pl

a "std-extra" group of libraries that are "this doesn't belong in the stdlib because it's not a vocabulary type, but it's a important part of the ecosystem" would be nice (it is Very Useful to be able to make breaking changes, external libraries can be versioned independently, the stdlib cannot)

some crates are maintained by the rustc devs (quite a lot actually, assuming that's what https://crates.io/users/rust-lang-owner means)

0
0
1