fix(lock): pass-through #[spec_locked] at compile time - #1
Merged
Merged
Conversation
With sibling blvm-spec present, synthesizing #[ensures] from EvalScript
§5.2 prose produced empty/broken attrs and spilled tokens after the
attribute ("expected item after attributes" on rustc 1.88). Keep the
attribute as a source marker for cargo-spec-lock verify; do not emit
contracts at compile time. Runtime consensus unchanged.
CI Test/Clippy use -D warnings; the pass-through path left Contract, ContractType, SpecSection, section_id_subsumes_formula_section, and Span unused in macro_impl.rs.
Member
Author
|
Pushed unused-import cleanup for CI |
Pre-existing cargo fmt --check failures on CI (not the pass-through).
Member
Author
|
Pushed CI |
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
1 participant
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
#[spec_locked]a compile-time pass-through when expanding.cargo check/cargo testwith siblingblvm-spec(EvalScript §5.2 was emitting brokenensuresfrom prose).cargo-spec-lock verifystill reads source markers. No consensus behavior change.Test plan
cargo check -p blvm-consensuswith path-patched localblvm-spec-lock→ OKcargo test --test engineering_suite test_csv_(companion fixture PR)Companion: BTCDecoded/blvm-consensus#11