Skip to content
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

[Documentation][IDE] Add a reference to the docs for the intellij-move IDE #37

Open
mkurnikov opened this issue Feb 1, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@mkurnikov
Copy link
Contributor

There's a project called intellij-move which is Move Language Plugin for Jetbrains IDEs. It supports all of them, including the free PyCharm Community. IDE should suggest installing it when any .move file is opened, or just download it from the Marketplace in Settings -> Plugins section.
We started it in the middle of 2020, and now it's in quite good shape.

Supported features are:

  • Parsing of both Move language and MSL
  • Name resolution in Move and MSL
  • Types and type inference in Move
  • Autoformatter
  • Support for Move.toml, move-cli commands, local deps, git deps (partially)

It would be great to have some official recognition of the project, maybe add a link in the docs.

I know Diem started their own language server at https://github.com/diem/move/tree/main/language/move-analyzer, based on rust-analyzer libraries, but it has only some initial implementation. At Pontem, we tried this approach too (code at move-language-server) but it was scrapped when we realized that Diem has started move-analyzer. It has a little bit of parser implemented, I can try to finish the parser later and merge it upstream if needed.

@mkurnikov mkurnikov added the bug Something isn't working label Feb 1, 2022
@sblackshear
Copy link
Contributor

That sounds excellent, thanks for the info @mkurnikov!

@vgao1996 @modocache: I don't have the most context on the status of move-analyzer, but wanted to tag you all to see if bringing in the parser from Pontem's vscode plugin could help.

sahithiacn pushed a commit to sahithiacn/move that referenced this issue Jan 11, 2023
* [move-compiler][move-stdlib] Switch to vector bytecode instructions

- Add annotation for native functions that are bytecode instructions
- Add compiler support for swapping those annotated functions to known bytecode instructions

* fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

* fixup! fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

* fixup! fixup! fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

* fixup! fixup! fixup! fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

Signed-off-by: sahithiacn <[email protected]>
sahithiacn pushed a commit to sahithiacn/move that referenced this issue Jan 11, 2023
* [move-compiler][move-stdlib] Switch to vector bytecode instructions

- Add annotation for native functions that are bytecode instructions
- Add compiler support for swapping those annotated functions to known bytecode instructions

* fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

* fixup! fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

* fixup! fixup! fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

* fixup! fixup! fixup! fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

Signed-off-by: sahithiacn <[email protected]>
bors-diem pushed a commit that referenced this issue Jan 11, 2023
* [move-compiler][move-stdlib] Switch to vector bytecode instructions

- Add annotation for native functions that are bytecode instructions
- Add compiler support for swapping those annotated functions to known bytecode instructions

* fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

* fixup! fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

* fixup! fixup! fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

* fixup! fixup! fixup! fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

Signed-off-by: sahithiacn <[email protected]>
Closes: #325
bors-diem pushed a commit that referenced this issue Jan 11, 2023
* [move-compiler][move-stdlib] Switch to vector bytecode instructions

- Add annotation for native functions that are bytecode instructions
- Add compiler support for swapping those annotated functions to known bytecode instructions

* fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

* fixup! fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

* fixup! fixup! fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

* fixup! fixup! fixup! fixup! [move-compiler][move-stdlib] Switch to vector bytecode instructions

Signed-off-by: sahithiacn <[email protected]>
Closes: #325
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants