-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Bug][Compiler-v2] GLOBAL_REFERENCE_ERROR error due to invalid acquiring of resource #13146
Labels
bug
Something isn't working
compiler-v2-stable
compiler-v2
stale-exempt
Prevents issues from being automatically marked and closed as stale
Comments
rahxephon89
added
bug
Something isn't working
stale-exempt
Prevents issues from being automatically marked and closed as stale
compiler-v2
labels
May 1, 2024
wrwg
added a commit
that referenced
this issue
May 30, 2024
Closes #13146 Adds a check that a global resource is not borrowed when it is declared in the access specifier list of a function. This implements the full semantics of Move 2.0 access specifiers. However, if the 2.0 language is not enabled, access specifiers other then `acquires` will be rejected by the context checker, and for that special case the behavior is equivalent. In order to test the extended access specifier semantics, we need to disable the existing acquires checker, which is not yet implemented for general access specifiers.
wrwg
added a commit
that referenced
this issue
May 30, 2024
Closes #13146 Adds a check that a global resource is not borrowed when it is declared in the access specifier list of a function. This implements the full semantics of Move 2.0 access specifiers. However, if the 2.0 language is not enabled, access specifiers other then `acquires` will be rejected by the context checker, and for that special case the behavior is equivalent. In order to test the extended access specifier semantics, we need to disable the existing acquires checker, which is not yet implemented for general access specifiers.
15 tasks
wrwg
added a commit
that referenced
this issue
May 30, 2024
Closes #13146 Adds a check that a global resource is not borrowed when it is declared in the access specifier list of a function. This implements the full semantics of Move 2.0 access specifiers. However, if the 2.0 language is not enabled, access specifiers other then `acquires` will be rejected by the context checker, and for that special case the behavior is equivalent. In order to test the extended access specifier semantics, we need to disable the existing acquires checker, which is not yet implemented for general access specifiers.
wrwg
added a commit
that referenced
this issue
May 30, 2024
Closes #13146 Adds a check that a global resource is not borrowed when it is declared in the access specifier list of a function. This implements the full semantics of Move 2.0 access specifiers. However, if the 2.0 language is not enabled, access specifiers other then `acquires` will be rejected by the context checker, and for that special case the behavior is equivalent. In order to test the extended access specifier semantics, we need to disable the existing acquires checker, which is not yet implemented for general access specifiers.
JoshLind
pushed a commit
that referenced
this issue
May 30, 2024
Closes #13146 Adds a check that a global resource is not borrowed when it is declared in the access specifier list of a function. This implements the full semantics of Move 2.0 access specifiers. However, if the 2.0 language is not enabled, access specifiers other then `acquires` will be rejected by the context checker, and for that special case the behavior is equivalent. In order to test the extended access specifier semantics, we need to disable the existing acquires checker, which is not yet implemented for general access specifiers.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
compiler-v2-stable
compiler-v2
stale-exempt
Prevents issues from being automatically marked and closed as stale
🐛 Bug
When compiling the following code:
V2 will generate bytecode verification error:
While V1 generates the following compilation error:
The text was updated successfully, but these errors were encountered: