fix: import path error and improper object initialization #6
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
intls
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
The import path "matchstick-as/assembly/index" is incorrect. The correct module to import is "matchstick-as". Using an incorrect path can lead to compilation errors because the system will not be able to find the specified module. The matchstick-as documentation recommends importing directly from "matchstick-as" without adding additional paths.
In AssemblyScript, to create an instance of BigInt, you need to use static methods such as BigInt.fromI32(), instead of the constructor new BigInt(0), which is not supported. Incorrect creation of BigInt will result in compilation or runtime errors.