Upgrade to 2.7.0

[gaetbout]

Pull Request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build-related changes
• Documentation content changes
• Other (please describe):

What is the new behavior?

Made some function deprecated.
Upgrade the code to 2.7
Fixed all warnings
Tried to make some fn generic (didn't look through all of em)
Replaced some while pop_front to for loop
Updated all assert to assert! and removed their error message as the default one is a good enough default value

[gaetbout]

@0xLucqs Ready for review.
An upgrade to latest edition should still be performed, will open an issue

[0xLucqs]

^

[milancermak]

Random things I've noticed (not necessarily enabled by 2.7.0):

• in bytes/src/utils.cairo, uint_min can be removed, replaced by core::cmp::min
• there's probably something that can be done with iterators on ByteReader, Queue, Stack, Vec and elsewhere(?)

Since we now have const arrays (❤️ dw ❤️), IMO it's worth adding optimized pow2 and pow10 as these are the most commonly used power functions. Even in Alexandria, all the bitshift fns use pow(2, n).

[gaetbout]

Random things I've noticed (not necessarily enabled by 2.7.0):

• in bytes/src/utils.cairo, uint_min can be removed, replaced by core::cmp::min
• there's probably something that can be done with iterators on ByteReader, Queue, Stack, Vec and elsewhere(?)

Since we now have const arrays (❤️ dw ❤️), IMO it's worth adding optimized pow2 and pow10 as these are the most commonly used power functions. Even in Alexandria, all the bitshift fns use pow(2, n).

• updated utils.cairo
• y, but I'd leave it for another PR as those are "extra" changes and this PR is big enough

Also would leave for another PR 😅 , please open an issue for that

[enitrat]

@gaetbout we should suppress the warnings on compilation otherwise it's going to appear on all dependent repositories

[gaetbout]

I removed all warnings that are from the code of alexandria lib.
I believe the new warnings are from using now deprecated Alexandria stuff

[enitrat]

my point is: what currently is used inside alexandria itself should not be triggering warnings

[gaetbout]

Ok, I understood your point thanks!
Will look into it when I have some time.
Nice to have lots of eyes on this 😃

[gaetbout]

@0xLucqs ?

[gaetbout]

@0xLucqs ? :D

[0xLucqs]

I want @milancermak to approve as well

[milancermak]

LGTM! Leaving just a bunch of nits.

If you fancy, there's a bunch of places where the while-let can be updated to a for-in (e.g. in array_ext.cairo or sha256.cairo, though the latter is deprecated, so meh).