[racket-dev] RFC: Coding Guidelines

From: John Clements (clements at brinckerhoff.org)
Date: Tue Aug 17 16:24:12 EDT 2010

On Aug 17, 2010, at 3:57 PM, Jay McCarthy wrote:

> We're attempting to write down coding guidelines for the project.
> Here is a first attempt:
> http://faculty.cs.byu.edu/~jay/tmp/201008161509-guidelines.html
> Please comment.

You write 

"As long as your code fulfills its promises and meets each of these criteria, you can push incrementally.

For example, I may be working on adding an exhaustive queue library to Racket. I imagine supporting 30 different functions across 5 different queue implementations. I don't have to wait to push until all 150 function implementations are documented, tested, and stressed. I can push whenever I make progress on each of the required points."

Either this is contradictory, or I'm misunderstanding it.  The first paragraph suggests that the code must meet each of the criteria; the second suggests that as long as it's *closer* to meeting the required criteria, it's fine.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4669 bytes
Desc: not available
URL: <http://lists.racket-lang.org/dev/archive/attachments/20100817/c9c3e0f5/attachment.p7s>

Posted on the dev mailing list.