Extract result into its own file
Extract result specs into their own file

Pull common code into spec helper
Namespace all tests on the class methods under it specifically
Fix private declaration for docs
Make the private methods actually be private

Really, I'm kind of wanting to pull them out into their own classes,
but that would add a lot of files, since the whole thing is like 200 loc,
it doesn't seem to merit that much ceremony. We'll see how I feel about it
as I keep up w/ the lib.
Refactoring and wording
A mock object

Plus some tests to allow it to be a suitable mock for development,
so that you don\'t have to hit the real server over and over.
Mock executes code using open3
Mock blows up when there is no language

Shares fetc/raise code with real implementation
Mock records the exitstatus
Mock records the language
Mock records the code
Mock records the url as https://eval.in/207744.json

So that it is a real url, that will behave basically correctly in most use cases,
but if you go there, it will tell you it is mock output rather than something really confusing
Mock sets the status

Extract the regex from the EvalIn specs into the spec helper
so all specs can share it.
Mock delegates fetch_result to real EvalIn

(I figure a get request isn't a big deal, but constantly hitting the service
with real values is pretty meh)
Rename tempfile path

Spaces in filenames are known to cause issues.
Can inject a proc to handle the call

This allows for any arbitrary behaviour to be injected
without me having to figure out what it might be ahead of time.
Mock can take a proc to handle the fetch_result

For same reasons as explained about on_call proc.
Normalize the fetch_result to use the on_fetch_result callback
Normalize the call body to use the on_call callback
Fix bug in test from making the methods actually private

...yeah, I think I actually want to extract these methods into classes