Skip to content
This repository has been archived by the owner on May 4, 2024. It is now read-only.

aptos-move-analyzer 0.1.0 is not sync with the last version 2.4.0 #1093

Open
spielcrypto opened this issue Jan 11, 2024 · 1 comment
Open
Labels
bug Something isn't working

Comments

@spielcrypto
Copy link

spielcrypto commented Jan 11, 2024

🐛 Bug

With the last version apt move 2.4.0 my vscode complains if I use the new loop for also I don't autocomplete and I cannot go
to any reference anymore

To reproduce

Code snippet to reproduce
install apt move 2.4.0
install aptos-move-analyzer 0.1.0
add the extension aptos-move-analyzer 0.1.0 in vscode

Stack trace/error message
error if I use the new loop for:

: unexpected token
   │78 │     for (i in 0..n) {   │         -  ^ Expected ')'   │         │      │         To match this '('""

Expected Behavior

Vscode should not complain about new loop for, autocomplete and go to reference should work again

System information

Please complete the following information:

  • Move Version: 2.4.0
  • Rust Version: 1.74.1
  • Computer OS: Manjaro Linux
  • aptos-move-analyzer version: 0.1.0
  • aptos-move-analyzer vscode extension: 0.1.0
@spielcrypto spielcrypto added the bug Something isn't working label Jan 11, 2024
@spielcrypto
Copy link
Author

spielcrypto commented Jan 15, 2024

with versions:

  • aptos-move-analyzer version: 0.1.1
  • aptos-move-analyzer vscode extension: 0.1.1

I still have the same issues

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant