Wanted: $50 / fix: ruby_parser fixes Dead or Alive
Published 2011-09-30 @ 19:29
A quick transcript of my rubyconf 2011 lightning-talk slides:
We all know and love ParseTree, but it sorta sucks:
| runs on 1.8 | runs on 1.9
|
|---|
| parses 1.8 | ✓ | ✗
|
|---|
| parses 1.9 | ✗ | ✗
ruby_parser gets us much closer by running on 1.9 (and every ruby implementation under the sun):
| runs on 1.8 | runs on 1.9
|
|---|
| parses 1.8 | ✓ | ✓
|
|---|
| parses 1.9 | ✗ | ✗
We have lots of tests and they run _really_ fast. On 1.9 we have 16 non-passing test cases:
10009 % rake19
Test run options: --seed 8509
Loaded suite -e
Started
...........................................................................
...........................................................................
...........................................................................
...........................................................................
...E............................F...........................E..............
E.......................F..................................................
....................E....F.....E..EF.......................................
.....F.................................................F...................
.....E........................E.......................E.......E............
............................
Finished in 0.355610 seconds.
1) Error:
Oh dear god the errors...
703 tests, 3847 assertions, 6 failures, 10 errors, 0 skips
Test run options: --seed 8509
Wanted: 6 Failures, 10 Errors -- dead or alive
$50 / fix
(First solution per failure wins)
[fork][1], fix, push, and submit pull request
Requirements:
1. gem install isolate
2. rake
3. there is no step 3
I'm available to help you get started
[1]: https://github.com/seattlerb/ruby_parser
|
|---|
|
|---|