-
Notifications
You must be signed in to change notification settings - Fork 38
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
refactor: move gw-types
and gw-common
to gwos
folder
#905
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jjyr
force-pushed
the
renaming-fields
branch
2 times, most recently
from
December 13, 2022 10:30
7d84d1d
to
c7ff6b9
Compare
jjyr
force-pushed
the
renaming-fields
branch
from
December 13, 2022 10:35
c7ff6b9
to
9088f20
Compare
blckngm
reviewed
Dec 13, 2022
jjyr
force-pushed
the
renaming-fields
branch
from
December 13, 2022 11:04
9088f20
to
125386a
Compare
jjyr
force-pushed
the
renaming-fields
branch
from
December 13, 2022 12:41
96a4bf8
to
9f0d992
Compare
What's the purpose of this change? |
jjyr
force-pushed
the
renaming-fields
branch
from
December 14, 2022 02:07
9f0d992
to
cad7bea
Compare
By moving these crates into |
jjyr
force-pushed
the
renaming-fields
branch
from
December 15, 2022 02:22
15957a0
to
dbc8d16
Compare
blckngm
previously approved these changes
Dec 15, 2022
…d_timepoint_to_since
jjyr
force-pushed
the
renaming-fields
branch
from
December 15, 2022 10:10
72506b4
to
7416271
Compare
jjyr
force-pushed
the
renaming-fields
branch
from
December 15, 2022 11:44
fde71ae
to
a4a0ac4
Compare
jjyr
force-pushed
the
renaming-fields
branch
from
December 15, 2022 11:56
a4a0ac4
to
ebba812
Compare
jjyr
force-pushed
the
renaming-fields
branch
from
December 16, 2022 04:36
7571e4d
to
7b444dc
Compare
zeroqn
approved these changes
Dec 19, 2022
blckngm
approved these changes
Dec 19, 2022
Merged
jjyr
added a commit
that referenced
this pull request
Dec 19, 2022
* refactor: move `gw-types` and `gw-common` to `gwos` folder * fix(ci): install nightly rustfmt * fix: prevent to get a early since value in global_state_last_finalized_timepoint_to_since * fix(ci): script-tests c-uint256-tests * refactor: move smt from `gw-common` to a standalone crate `gw-smt` * refactor: remove tron account lock contract * chore: remove unused step from CI * refactor: define H256 as alias of [u8; 32] * refactor: remove unused files from gw-smt * refactor: reduce copy when convert Vec<SMTH256> * fix(ci): fix molecule schema url * fix: fix evm tests * fix: gwos-evm tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
gw-types
andgw-common
to thegwos
folder. Then we can directly referent them in the contract by the path.gw-common
to a standalone crategw-smt
, so we can simplify the dependency of rust contracts.capsule
toolchain tonightly-2021-08-16
gwos/contracts/tron-account-lock
. Tron lock is not enabled both in the testnet and mainnet.gw_utils::block_timepoint
togw_utils::finalized_timepoint