fix issue where libraries would get loaded at extreme timestamps and block numbers, also switch to the new hevm stripBytecodeMetadata #510
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.
loadLibraries
would use(initialTimestamp, initialBlockNumber)
as the delay property, causingblock . number
andblock . timestamp
to be incremented way more times than desired. we introduce a newinitialVM
that takes care of all this business for us so we can just use(0, 0)
, as well as extend the timestamp and block number business to theRPC
(multicontract, we should probably also rename this) module.hevm-0.37 contains the new
stripBytecodeMetadata
that actually works and is a copy of the version i introduced a while back, so we remove that bit of duplicated code as well.