Hereās some commentary about the āsimple cratesā:
16:32 simple crates - there are a number of unbelievably common functions i end up reimplementing a lot
16:32 and poorly
16:33 copy_dir is just a recursive directory copy. not sure if thereās a good crate for this yet
16:34 sometimes one needs to do a copy but ignoring dotfiles. i open code this with walk_dir
16:34 but there should be a common copy_dir that covers most cases and just works
16:34 remove_dir_all is broken in std on windows
16:34 so people always reimplement in
16:34 *it
16:35 while it should be fixed in std, in the meantime somebody should just publish a working version
16:35 dojob is a common routine that cargo, rustbuild and rustup use to create process groups on Windows for killing multiple processes
16:35 but they all implement it diferently and some are missing fixes
16:36 symlink_dir would be a crate that creates symlinks to directories correctly on windows, using directory junctions
16:37 homedir would be an implementation of std::env::home that uses cargo/rustupās definition. I consider std incorrect when it considers HOME on Windows.
It's not the service itself that is proprietary, but a service for regression testing proprietary Rust projects, to give us visibility into the ecosystem where we are lacking it. It would be a formal structure for setting up NDAs and compensation for running cargobomb and similar future efforts on closed-source projects.
As a once and future (hopefully with rust) "Enterprise Software Developer"ā¢, I think this could go a long way towards reassuring companies that they could rely on rust for their development future.
What does it actually entail? Hope explaining what it entails doesnāt take as long as actually doing it.
From the single line, I assume it has to do with measuring performance of the compiler over its development history. Sounds related to continuous integration/testing/benchmarking. Would this use gperf? Which benchmarks would you use to measure this?
@pmatos The main idea is just to get information about the performance of the Rust compiler in front of people on a regular basis, to build a sense of accountability. At the time I would have said to examine perf.rust-lang.org to extract a sensible story about what happened last week, and just write it up in a consistent way, with key metrics. At the moment though perf.rlo is not workingā¦
Templates was pulled out pending an RFC. The feedback in a pre-RFC thread suggests that people donāt want it in cargo but would rather an external cargo tool like clippy.
