Stream: t-compiler

Topic: mcve-tag for "contributions wanted"


oli (May 11 2019 at 13:45, on Zulip):

I just saw https://github.com/rust-lang/rust/issues/60725, which is quite a big example with loads of macros and other noise. We've had such situtations in the past, where a fairly large repro was given, but a smaller one would be preferrable. What do you folks think about adding a E-needs-mcve label to be used in conjuncture with E-help-wanted?

centril (May 11 2019 at 13:53, on Zulip):

I like it!

Jake Goulding (May 11 2019 at 14:18, on Zulip):

I'm always looking for a way to improve https://stackoverflow.com/tags/rust/info (see "Producing a Minimal, Complete, Verifiable example for Rust code")

Jake Goulding (May 11 2019 at 14:18, on Zulip):

I've thought about extracting it to a separate repo for the purposes of being able to link to it better. If it would actually be useful outside of SO, that'd be even better.

centril (May 11 2019 at 14:22, on Zulip):

@Jake Goulding Yeah I think we can link to that one, looks like good advice for bug reports as well

Jake Goulding (May 11 2019 at 14:23, on Zulip):

@centril link to it where it is now, or in a separate repo?

centril (May 11 2019 at 14:23, on Zulip):

@Jake Goulding Up to you :slight_smile: A wiki entry is another possibility

centril (May 11 2019 at 14:23, on Zulip):

or a rustc-guide page

Jake Goulding (May 11 2019 at 14:39, on Zulip):

A wiki entry whereabouts? I'd have concerns about a rustc-guide page, mostly because I'd be afraid that SO folk would see that and go "I'm not touching the compiler!"

centril (May 11 2019 at 14:47, on Zulip):

@Jake Goulding How about this:

1. A wiki entry on rust-lang/rust
2. rustc guide links to that;
3. SO possibly also?

centril (May 11 2019 at 14:47, on Zulip):

I'd be happy with linking to SO as well

Jake Goulding (May 11 2019 at 14:47, on Zulip):

Yeah, definitely linking to one place feels the best.

centril (May 11 2019 at 14:48, on Zulip):

@Jake Goulding the content on SO seems polished and such -- maybe just include a bit of info about rust-lang/rust bugs?

Jake Goulding (May 11 2019 at 14:49, on Zulip):

I'm leaning towards a separate repo (say shepmaster/mcve), only so that the permissions can be really distinct from the tight ones for rust-lang/rust. For example, we also have some tips for creating MCVEs for Diesel that could live there but wouldn't make sense in rust-lang/rust.

Jake Goulding (May 11 2019 at 14:50, on Zulip):

Do you feel like there's any objection to linking to such a resource from official places like the rust-lang repo or rustc-guide?

centril (May 11 2019 at 14:50, on Zulip):

@Jake Goulding works for me; tho rust-lang/mcve might be "more official" (users might care about that?)

centril (May 11 2019 at 14:50, on Zulip):

I don't have any objections myself

Jake Goulding (May 11 2019 at 14:50, on Zulip):

Would such a repo allow for crate-specific tips as well?

centril (May 11 2019 at 14:51, on Zulip):

I don't see why not

centril (May 11 2019 at 14:51, on Zulip):

we can iterate :P

nikomatsakis (May 13 2019 at 17:39, on Zulip):

I just saw https://github.com/rust-lang/rust/issues/60725, which is quite a big example with loads of macros and other noise. We've had such situtations in the past, where a fairly large repro was given, but a smaller one would be preferrable. What do you folks think about adding a E-needs-mcve label to be used in conjuncture with E-help-wanted?

I am strongly in favor of this

oli (May 13 2019 at 17:50, on Zulip):

I'll create the label, so far noone has objected

Jake Goulding (May 13 2019 at 19:11, on Zulip):

I'll try to create a place to link to soon!

Last update: Nov 20 2019 at 01:25UTC