Allow _zero_for_deref to be defined in Pulse#685
Merged
tahina-pro merged 3 commits intofstar2from Mar 16, 2026
Merged
Conversation
as an alternative to C._zero_for_deref, in preparation for the deprecation of Low* This commit maintains compatibility with EverParse.
…a_pulse_zero_for_deref
Collaborator
|
Great, thank you. |
This was referenced Mar 19, 2026
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
2 participants
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.
This PR allows Pulse to define its own
_zero_for_deref, a special array index to tell Karamel to compile array accesses using that index as pointer dereferences. Having it defined in Pulse severs the dependency over Low* KrmlLib.FStarLang/pulse#592FStarLang/FStar#4120 (of which this PR is a companion) defines_zero_for_derefinPulse.Lib.Pervasives