Skip to content

Conversation

@awelc
Copy link
Contributor

@awelc awelc commented Dec 19, 2025

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:

image

When the compiler was modified to preserve the necessary data (#24645), we could fix this in move-analyzer as well:

image

Test plan

Test output has been updated to reflect new display format. All tests must pass

@awelc awelc requested review from cgswords and dariorussi December 19, 2025 14:44
@awelc awelc self-assigned this Dec 19, 2025
@awelc awelc temporarily deployed to sui-typescript-aws-kms-test-env December 19, 2025 14:44 — with GitHub Actions Inactive
@vercel
Copy link

vercel bot commented Dec 19, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
sui-docs Ready Ready Preview, Comment Dec 22, 2025 1:16pm
2 Skipped Deployments
Project Deployment Review Updated (UTC)
multisig-toolkit Ignored Ignored Preview Dec 22, 2025 1:16pm
sui-kiosk Ignored Ignored Preview Dec 22, 2025 1:16pm

pub edition: Option<Edition>,
/// Compiler analysis info
pub compiler_analysis_info: Option<CompilerAnalysisInfo>,
pub compiler_analysis_info: CompilerAnalysisInfo,
Copy link
Contributor Author

@awelc awelc Dec 19, 2025

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();
Copy link
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants