v0.4.3

Wait, I thought every process exited with some code???

Summary

This release fixes a sneaky little bug that was caused when the code ran on pistons end was SIGKILLED causing the exit code to be null.

Changes:

• ExecResult.code is now an Option<isize>.

I suppose the process will be exiting with Some(code) after all 😮

---

Full Changelog: v0.4.2...v0.4.3

v0.4.2

Yay, now we can use existing files on disk!

What's Changed

• Add ability to create File objects from existing files (#11) by @parafoxia in #12

Full Changelog: v0.4.1...v0.4.2

v0.4.1

But what if I want to run my own instance of Piston?

Summary

This release adds the with_url and with_url_and_key methods to Client to facilitate making requests to your own instance of Piston, if you run one.

What's Changed

• Add Client::with_url and Client::with_url_and_key by @y21 in #10

Full Changelog: v0.4.0...v0.4.1

v0.4.0

Is it ok, or is it an err?

Summary

This release differentiates between what is_ok and is_err do on ExecResult and ExecResponse. Previously ExecResponse would be an err if the exit code of the execution was not 0, now it is based on the http status returned by Piston.

Additions

• Status field added to ExecResponse.
• Testing for ExecResponse.

Changes

• Stdout field will now be an empty string if a non-200 status is received from Piston.

Full Changelog: v0.3.0...v0.4.0

v0.3.0

Bye bye openssl, hello rustls

What's Changed

• Move from openssl to rustls by @Jonxslays in #5
• Various docstring clarifications
• Default Executor.version to "*"

Full Changelog: v0.2.3...v0.3.0

v0.2.3

impl Clone for Client { ... }

Summary

This release implements the Clone trait for Client. (Not having it was an oversight.)

v0.2.2

We don't like errors, but they happen anyways.

Summary

This release focuses on simplifying the handling of errors by making the interface more consistent.

Breaking changes

• Removed message field from ExecResponse, the data that would be stored there is now stored in stdout, stderr, and output on responses where message would have been Some. Now the user will not have to check for the existence of message, they can just use any of the already guaranteed fields on the response.

Additions

• HTTP status code is now included in non 200 response error messages.
• Language and version are now always passed back with the response, previously they would be an empty string on non 200 responses.
• Updated examples with cleaner, more accurate error handling.

Bugfixes

• is_ok and is_err on ExecResult and ExecResponse now properly determine status using the process status code rather than stdout, and stderr.

Full Changelog: v0.2.1...v0.2.2

v0.2.1

Another documentation patch, your favorite.

Summary

This release hides test function signatures in the async examples, making them a bit cleaner.

Full Changelog: v0.2.0...v0.2.1

v0.2.0

Documentation++

Summary

This release adds some additional documentation, test coverage, and condenses the names of some structs.

Breaking changes

• ExecutorResponse renamed to ExecResponse.
• ExecutionResult renamed to ExecResult.

Full Changelog: v0.1.0...v0.2.0

v0.1.0

Initial release

Additions

• Client
• Executor
• ExecutorResponse
• ExecutionResult
• File
• Runtime

Along with these structs come their methods which make interacting with Piston easier.
Check out the documentation for a more detailed breakdown.
🚀 Happy coding!