[cmpitg]

How do you make sure the correctness of the implementations? Shouldn't there be tests?

[kennyledet]

Precisely. This is something that I have plans on implementing, but obviously I don't have the whole day 24/7 to manage this repo man. I'm doing other things right now (work), that's why I took so long to even answer the initial comments in this thread.

[ericHosick]

Tests and behavior should be defined before the code.

I recommend you comment out all code, write the tests and then un-comment the code line by line.

This not only tests the code, but tests the tests and assures that you are covering the edge cases the code contains already.

[kennyledet]

Update: Unit tests are now a convention.

[goldenkey]

The code is the test. If the code runs without compilation errors, then use it for healthcare.gov </sarcasm>

[kennyledet]

You forgot to open the the sarcasm tag :)

[goldenkey]

That's part of the hidden DOM. Implicit. ;-)

[kennyledet]

Sorry, but explicit > implicit for markup.

Btw, how's that repo going? :)

[goldenkey]

Sorry, haven't started it yet ;-)