Add PIET to the list of Solidity tools

[hellraiserinchief]

Description

Checklist

• Code compiles correctly
• All tests are passing
• New tests have been created which fail without the change (if possible)
• README / documentation was extended, if necessary
• Changelog entry (if change is visible to the user)
• Used meaningful commit messages

[chriseth]

Our tests are complaining about trailing whitespace here - can you please check?

Test failures

[hellraiserinchief]

All checks seem to pass now

[chriseth]

Could you please squash it into a single commit?

[erak]

@hellraiserinchief Could you please rebase? We just fixed the broken MacOS build on Circle which led to the failing test on this PR.

[erak]

I'm sorry, but the commits are bit messed up and do appear twice. Did you rebase onto develop? Do you need help with this?

[hellraiserinchief]

I'm sorry, but the commits are bit messed up and do appear twice. Did you rebase onto develop? Do you need help with this?

Yeah, help would be welcome, I am new to contributing to OSS

[hellraiserinchief]

I'm sorry, but the commits are bit messed up and do appear twice. Did you rebase onto develop? Do you need help with this?

Yeah, help would be welcome, I am new to contributing to OSS

I have tried combined the commits into a single commit, please have a look and advice.

[chriseth]

Sorry, I fear you have to rebase again, the macos version change should be part of a different PR.

[erak]

As @chriseth already mentioned, this needs to be rebased again, such that the changes to .circleci/config.yaml are not part of the PR. Also, since your working on develop of your fork, I'd strongly recommend to create a branch in your forked repository, and then open a PR with our develop as the target and your branch as the source. Your current workflow might lead to issues when trying to keep your fork up to date. Please see https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/syncing-a-fork for further advice.

[erak]

@hellraiserinchief Could you also remove the change to .circleci/config.yml? Otherwise this PR looks good!

[hellraiserinchief]

@erak, I will follow your advice and create a new branch to submit a new PR, instead of using the develop branch directly