feat: library improvements

[enitrat]

Closes #2395
Closes #2392

Introduced changes

• Replaced all @Array<T> by Span<T>
• Replaced useless Clone derivation by Copy
• Updated .tool-version to scarb 2.7.1 (and re-formatted)
• Exposed with pub some attributes (no effect)
• Derived Debug on some items

How to adapt your codebase:

Search and replace with regex:

deploy\(@array!\[(.*?)\]\)
deploy([$1].span())

deploy\(@ArrayTrait::new()\)
deploy([].span())

deploy\(@(.*?)\)
deploy($1.span())

deploy_at\(@ArrayTrait::new()\)
deploy_at([].span())

deploy_at\(@array!\[(.*?)\]\)
deploy_at([$1].span())

deploy_at\(@(.*?)\)
deploy_at($1.span())

precalculate_address\(@array!\[(.*?)\]\)
precalculate_address([$1].span())

precalculate_address\(@ArrayTrait::new()\)
precalculate_address([].span())

precalculate_address\(@(.*?)\)
precalculate_address($1.span())






Checklist

• Linked relevant issue
• Updated relevant documentation
• Added relevant tests
• Performed self-review of the code
• Added changes to CHANGELOG.md

[enitrat]

any idea how I can debug what fails in the deploy_at and trace tests?

[cptartur]

Hey, thanks for the PR, but first we want to figure out a way we can introduce changes to snforge_std in a less breaking manner as it is becoming an increasingly bigger concern.

We're happy to merge the non breaking improvements.

[enitrat]

Hi @cptartur sure, let me know. Perhaps you could use the #[deprecated()] attributes and keep old items at the same time.

[enitrat]

opened #2421 for non breaking changes.