[racket] Does bug report advice apply to this mailing list - Don't include reference to collection(s)?

[Don Green]

I have been advised that when submitting bug reports I should not include
'required' statements that call my relevant collections.

Question 1:  Should I copy any required collections directly into a copy of
my module before sending it along with my question?  This would make the
code immediatly executable.

Q2: Does the same advice apply to submitting questions about code in this
mailing list?  My guess is that it might be acceptable to submit code
snipets as long as they are sufficient to be understood.  They might be
commented upon although they certainly could not be run as-is.
Thanks.

[Neil Van Dyke]

Don Green wrote at 05/14/2012 11:53 PM:
> I have been advised that when submitting bug reports I should not include
> 'required' statements that call my relevant collections.
>
> Question 1: Should I copy any required collections directly into a copy of
> my module before sending it along with my question? This would make the
> code immediatly executable.
>

For bug reports, it is good practice to try to provide a *pretty
minimal* example that a person looking at the bug report can use to
reproduce the bug. This good practice is not specific to Racket.

> Q2: Does the same advice apply to submitting questions about code in this
> mailing list? My guess is that it might be acceptable to submit code
> snipets as long as they are sufficient to be understood. They might be
> commented upon although they certainly could not be run as-is.
> Thanks.

I suggest using your judgment.

Neil V.

____________________
Racket Users list:
http://lists.racket-lang.org/users