chore: remove sway-libs dep from testing fixtures

[maschad]

Closes #2160

• Mocks the compute_bytecode functions in the sway contracts

[maschad]

@Dhaiwat10 @arboleya any ideas why this test would hang on CI? It works fine locally

[arboleya]

any ideas why this test would hang on CI? It works fine locally

Nothing I can see only by reading it.

[danielbate]

One concern here is the docs still references the sway std lib function, so we are miss communicating the dependency. If the sway std lib signature changed, we are not in sync as we have a mocked version. I think we should be more generally referencing this as working with bytes with both a Vec<u8> and Bytes example. Thoughts?

[maschad]

One concern here is the docs still references the sway std lib function, so we are miss communicating the dependency. If the sway std lib signature changed, we are not in sync as we have a mocked version. I think we should be more generally referencing this as working with bytes with both a Vec<u8> and Bytes example. Thoughts?

Whether it's mocked or not wouldn't have an effect as it relates to breaking changes as we would still be using a particular version as our dependency

the benefit with this at least would be should we try to upgrade, if there is a breaking change, Rust would let us know due to it's semver toolchain - but this would still be dependent on our manual attempt to upgrade.

In summary, I'm not sure if there is an uncomplicated way to discuss working with bytecode or Vec<u8> without using a concrete example from a sway library.

[danielbate]

Whether it's mocked or not wouldn't have an effect as it relates to breaking changes as we would still be using a particular version as our dependency

But agreed we should remove the dependency, like you have done.

In summary, I'm not sure if there is an uncomplicated way to discuss working with bytecode or Vec without using a concrete example from a sway library.

I would personally prefer removing the reference to the sway std lib in the docs and just more generally speak about bytecode.

Some functions require you to pass in bytecode to the function. The type of the bytecode parameter is usually `Vec<u8>`, this would be handled like so:

<-- code snippet -->

[maschad]

I would personally prefer removing the reference to the sway std lib in the docs and just more generally speak about bytecode.

2f6af7d

[github-actions]

Coverage Report:

Lines	Branches	Functions	Statements
79.54%(+0%)	69.84%(+0%)	77.12%(+0%)	79.65%(+0%)

Changed Files:

Coverage values did not change👌.