Default integer inference to native width - #9
Merged
Conversation
miselin
marked this pull request as ready for review
August 10, 2026 04:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Exact-width literal inference allowed values such as
0and1to becomei1. That could truncate inferred accumulators and make ordinary comparisons such as1 < 2behave incorrectly after lowering.This keeps unconstrained literals ergonomic while preserving a systems-language boundary:
i16_value + 70000is a compile-time error rather than a value-driven implicit widening.Validation
opam exec -- dune buildopam exec -- dune runtestgit diff --checkThe Nix CI gates were not run because
nixis unavailable in the current environment. Repository-widedune fmtis also blocked by pre-existing formatting drift; unrelated promoted formatting changes were reverted.