Jeff King wrote:
> On Tue, Jun 01, 2021 at 01:34:32AM -0500, Felipe Contreras wrote:
>
> > > > I use ruby to parse binary data from git all the time:
> > > >
> > > > git log --format='%b%x00' |
> > > > ruby -e 'ARGF.each("\0", chomp: true) { |chunk| p chunk }'
> > >
> > > I doubt we'd want to add a ruby dependency to our test suite, but sure,
> > > we could do the same thing with perl.
> >
> > I don't mean in the final patches, I mean while the patches are
> > being developed.
> >
> > Once it's clear what the code should do, and how to verify it's doing
> > what it's supposed to be doing, we can decide how the test suite should
> > verify it.
> >
> > Ruby is great for prototyping.
>
> If we are not worried about the test suite, then I would think viewing
> the output in "less" would be the simplest way to see that it's doing
> the right thing.
No, I meant you write the test case with ruby and once everything works
you decide how to replicate the same with something more widely
available.
Sometimes I decide to delete the test cases I used for prototyping
because they are too convoluted, test something very esoteric, or it's
not easy to do the same in CI infraestructure.
But they helped me write the code.
Cheers.
--
Felipe Contreras
