-
Notifications
You must be signed in to change notification settings - Fork 11.7k
[move-ide] Better on-hover value display for string constants #24704
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
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| pub edition: Option<Edition>, | ||
| /// Compiler analysis info | ||
| pub compiler_analysis_info: Option<CompilerAnalysisInfo>, | ||
| pub compiler_analysis_info: CompilerAnalysisInfo, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed this while implementing the core of this PR as it irked me that we had an unwrap for this so far away from where it is clear that the unwrap is OK
| CompiledProgram, | ||
| ) { | ||
| // run typing analysis for the main user program | ||
| let compiler_analysis_info = compiled_pkg_info.compiler_analysis_info.as_ref().unwrap(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the old unwrap that I mentioned in https://github.com/MystenLabs/sui/pull/24704/files#r2635378417 that I decided to remove in this PR outside of the PR's core logic as in this position it's tough to argue that it is safe without looking at a completely different part of the code baase
5b36ddc to
eef8e32
Compare
Description
What the subject says. Before, for byte vectors that are defined in source code using strings we were displaying byte values due to loss of some information during compilation:
When the compiler was modified to preserve the necessary data (#24645), we could fix this in
move-analyzeras well:Test plan
Test output has been updated to reflect new display format. All tests must pass