-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 3.3.0
with backwards compatibility fixes
#1284
Conversation
Sorry, will take a look at this tomorrow. We should get this out soon |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Main question I have has to do with the use of the *_compat
methods
Co-authored-by: Michael Müller <mich@elmueller.net> Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
3.3.0
with backward compatibility fixes3.3.0
with backwards compatibility fixes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just realized that this won't work.
We can't leave set_contract_storage
as is, we need to revert it to not return anything, otherwise code like:
#[ink(message)]
pub fn foo(&self) {
ink_env::set_contract_storage(&Default::default(), &1)
}
won't compile (even though it did in 3.0.1).
Instead of having the compat
functions we need with_size
functions (or something similarly named).
Nice catch! Fixed for
I renamed the user-facing api function. This should solve the issue I think. As a general rule, having |
Can you remove all the |
… Compatibility` docs section
Updated according to the discussed naming policy + added |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some small things, but we're almost there 💪
Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
also fixed spellcheck config (was done wrong in #1294) to make CI happy |
🦑 📈 ink! Example Contracts ‒ Changes Report 📉 🦑
These are the results when building the
Link to the run | Last update: Tue Jun 21 21:56:23 CEST 2022 |
Codecov Report
@@ Coverage Diff @@
## v3.x.x #1284 +/- ##
=========================================
Coverage ? 71.87%
=========================================
Files ? 178
Lines ? 5984
Branches ? 0
=========================================
Hits ? 4301
Misses ? 1683
Partials ? 0 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! @ascjones can you take a look before we merge it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Context: user-reported issues on our SE (first and second) unveiled backward incompatibility introduced in the 3.1.0 release.
The following has been done to restore backward compatibility:
eth_compatibility crate
[seal1] seal_set_storage
(this one is to restore compatibiliy between minor versions of ink! crates; see @HCastano SE answer in this regard)
All these reverted breaking changes are subject to be included in the upcoming MAJOR ink! release 4.
Meanwhile, to continue support and delivering fixes for ink! 3, branch v3.x.x was created from 3.2.0 tag.
This closes #1278.