-
Notifications
You must be signed in to change notification settings - Fork 159
refactor: use upstream core/types
#875
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
Merged
Parent:
chore(all): libevm phase 2.5
Merged
Conversation
This file contains hidden or 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
qdm12
approved these changes
Mar 14, 2025
darioush
approved these changes
Mar 14, 2025
michaelkaplan13
approved these changes
Mar 14, 2025
qdm12
pushed a commit
to ava-labs/subnet-evm
that referenced
this pull request
Mar 19, 2025
Complete the transition of `core/types` to upstream code. Note that the previous commit results in _all_ upstream types / vars / consts being in the `imports.go` file. This results in a strict partition of upstream and local identifiers so it is safe to simply change import paths. 1. Globally change all imports from `subnet-evm/core/types` to `libevm/core/types`; 2. Rename all `subnet-evm/core/types` imports to `customtypes` for ease of review here; 3. Dot import `libevm/core/types` in tests only to avoid hundreds of noisy changes. See original PR ava-labs/coreth#875
qdm12
pushed a commit
to ava-labs/subnet-evm
that referenced
this pull request
Mar 19, 2025
Complete the transition of `core/types` to upstream code. Note that the previous commit results in _all_ upstream types / vars / consts being in the `imports.go` file. This results in a strict partition of upstream and local identifiers so it is safe to simply change import paths. 1. Globally change all imports from `subnet-evm/core/types` to `libevm/core/types`; 2. Rename all `subnet-evm/core/types` imports to `customtypes` for ease of review here; 3. Dot import `libevm/core/types` in tests only to avoid hundreds of noisy changes. See original PR ava-labs/coreth#875
qdm12
pushed a commit
to ava-labs/subnet-evm
that referenced
this pull request
Mar 21, 2025
Complete the transition of `core/types` to upstream code. Note that the previous commit results in _all_ upstream types / vars / consts being in the `imports.go` file. This results in a strict partition of upstream and local identifiers so it is safe to simply change import paths. 1. Globally change all imports from `subnet-evm/core/types` to `libevm/core/types`; 2. Rename all `subnet-evm/core/types` imports to `customtypes` for ease of review here; 3. Dot import `libevm/core/types` in tests only to avoid hundreds of noisy changes. See original PR ava-labs/coreth#875
qdm12
pushed a commit
to ava-labs/subnet-evm
that referenced
this pull request
Mar 21, 2025
Complete the transition of `core/types` to upstream code. Note that the previous commit results in _all_ upstream types / vars / consts being in the `imports.go` file. This results in a strict partition of upstream and local identifiers so it is safe to simply change import paths. 1. Globally change all imports from `subnet-evm/core/types` to `libevm/core/types`; 2. Rename all `subnet-evm/core/types` imports to `customtypes` for ease of review here; 3. Dot import `libevm/core/types` in tests only to avoid hundreds of noisy changes. See original PR ava-labs/coreth#875
qdm12
pushed a commit
that referenced
this pull request
Mar 24, 2025
## Why this should be merged Complete the transition of `core/types` to upstream code. ## How this works Note that #872 results in _all_ upstream types / vars / consts being in the `imports.go` file. This results in a strict partition of upstream and local identifiers so it is safe to simply change import paths. 1. Globally change all imports from `coreth/core/types` to `libevm/core/types`; 2. Rename all `coreth/core/types` imports to `customtypes` for ease of review here; 3. Dot import `libevm/core/types` in tests only to avoid hundreds of noisy changes.
qdm12
pushed a commit
to ava-labs/subnet-evm
that referenced
this pull request
Mar 24, 2025
Complete the transition of `core/types` to upstream code. Note that the previous commit results in _all_ upstream types / vars / consts being in the `imports.go` file. This results in a strict partition of upstream and local identifiers so it is safe to simply change import paths. 1. Globally change all imports from `subnet-evm/core/types` to `libevm/core/types`; 2. Rename all `subnet-evm/core/types` imports to `customtypes` for ease of review here; 3. Dot import `libevm/core/types` in tests only to avoid hundreds of noisy changes. See original PR ava-labs/coreth#875
qdm12
pushed a commit
to ava-labs/subnet-evm
that referenced
this pull request
Mar 24, 2025
Complete the transition of `core/types` to upstream code. Note that the previous commit results in _all_ upstream types / vars / consts being in the `imports.go` file. This results in a strict partition of upstream and local identifiers so it is safe to simply change import paths. 1. Globally change all imports from `subnet-evm/core/types` to `libevm/core/types`; 2. Rename all `subnet-evm/core/types` imports to `customtypes` for ease of review here; 3. Dot import `libevm/core/types` in tests only to avoid hundreds of noisy changes. See original PR ava-labs/coreth#875
qdm12
pushed a commit
that referenced
this pull request
Mar 24, 2025
## Why this should be merged Complete the transition of `core/types` to upstream code. ## How this works Note that #872 results in _all_ upstream types / vars / consts being in the `imports.go` file. This results in a strict partition of upstream and local identifiers so it is safe to simply change import paths. 1. Globally change all imports from `coreth/core/types` to `libevm/core/types`; 2. Rename all `coreth/core/types` imports to `customtypes` for ease of review here; 3. Dot import `libevm/core/types` in tests only to avoid hundreds of noisy changes.
qdm12
pushed a commit
to ava-labs/subnet-evm
that referenced
this pull request
Mar 24, 2025
Complete the transition of `core/types` to upstream code. Note that the previous commit results in _all_ upstream types / vars / consts being in the `imports.go` file. This results in a strict partition of upstream and local identifiers so it is safe to simply change import paths. 1. Globally change all imports from `subnet-evm/core/types` to `libevm/core/types`; 2. Rename all `subnet-evm/core/types` imports to `customtypes` for ease of review here; 3. Dot import `libevm/core/types` in tests only to avoid hundreds of noisy changes. See original PR ava-labs/coreth#875
qdm12
pushed a commit
to ava-labs/subnet-evm
that referenced
this pull request
Mar 28, 2025
Complete the transition of `core/types` to upstream code. Note that the previous commit results in _all_ upstream types / vars / consts being in the `imports.go` file. This results in a strict partition of upstream and local identifiers so it is safe to simply change import paths. 1. Globally change all imports from `subnet-evm/core/types` to `libevm/core/types`; 2. Rename all `subnet-evm/core/types` imports to `customtypes` for ease of review here; 3. Dot import `libevm/core/types` in tests only to avoid hundreds of noisy changes. See original PR ava-labs/coreth#875
qdm12
pushed a commit
to ava-labs/subnet-evm
that referenced
this pull request
Apr 1, 2025
Complete the transition of `core/types` to upstream code. Note that the previous commit results in _all_ upstream types / vars / consts being in the `imports.go` file. This results in a strict partition of upstream and local identifiers so it is safe to simply change import paths. 1. Globally change all imports from `subnet-evm/core/types` to `libevm/core/types`; 2. Rename all `subnet-evm/core/types` imports to `customtypes` for ease of review here; 3. Dot import `libevm/core/types` in tests only to avoid hundreds of noisy changes. See original PR ava-labs/coreth#875
node-druidx56y
added a commit
to node-druidx56y/subnet-evm
that referenced
this pull request
Sep 28, 2025
Complete the transition of `core/types` to upstream code. Note that the previous commit results in _all_ upstream types / vars / consts being in the `imports.go` file. This results in a strict partition of upstream and local identifiers so it is safe to simply change import paths. 1. Globally change all imports from `subnet-evm/core/types` to `libevm/core/types`; 2. Rename all `subnet-evm/core/types` imports to `customtypes` for ease of review here; 3. Dot import `libevm/core/types` in tests only to avoid hundreds of noisy changes. See original PR ava-labs/coreth#875
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.
Why this should be merged
Complete the transition of
core/typesto upstream code.How this works
Note that #872 results in all upstream types / vars / consts being in the
imports.gofile. This results in a strict partition of upstream and local identifiers so it is safe to simply change import paths.coreth/core/typestolibevm/core/types;coreth/core/typesimports tocustomtypesfor ease of review here;libevm/core/typesin tests only to avoid hundreds of noisy changes.Note
This is part of a chain of PRs
and will have its base changed once #872 is merged. The chain is split so that each one is "obviously" correct. I will not consider any review changes that deviate from this simplicity—if this is an issue, please explain why and add a "Do not merge" label.How this was tested
CI of existing tests.
Need to be documented?
No
Need to update RELEASES.md?
No