Add harnesses for all functions in Alignment

[tautschnig]

In #33 a contract was added to Alignment::new_unchecked, but its verification was only implicit through Layout, and may be affected by future changes to the contract that was added to Layout. This commit remedies this by adding a separate harness just for Alignment.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

[celinval]

Looks good to me. Thanks

[feliperodri]

LGTM, but did you try the safety_constraint?

[tautschnig]

LGTM, but did you try the safety_constraint?

No, because I can't get Arbitrary to work in the first place, see #42 (comment). Perhaps all this will work when upgrading Kani?

[celinval]

LGTM, but did you try the safety_constraint?

No, because I can't get Arbitrary to work in the first place, see #42 (comment). Perhaps all this will work when upgrading Kani?

Please see my reply above

[celinval]

Why did you revert the impl Arbitrary? Isn't that what we want (except for the transmute call).

[tautschnig]

Why did you revert the impl Arbitrary? Isn't that what we want (except for the transmute call).

I thought it was causing the compile errors, but then I realised it’s #49 that’s needed. Will continue on this once Kani and this repo are back in a working state.

[tautschnig]

Why did you revert the impl Arbitrary? Isn't that what we want (except for the transmute call).

I thought it was causing the compile errors, but then I realised it’s #49 that’s needed. Will continue on this once Kani and this repo are back in a working state.

Now successfully using Arbitrary.