chore: sync project template skills with v0.16 - #1394
Merged
Merged
Conversation
Contributor
Miden examples benchmarkCandidate
SVG flamegraphs and compiled packages are attached to the workflow run. |
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.
Overview
This PR mirrors the merged project-template v0.16 skill migration into the compiler-bundled project template used by
cargo miden new. The standalone project-template copy was updated in 0xMiden/project-template#64, and this keeps the embedded compiler scaffold from lagging behind it.project template code placement
This also relates to #1373, where I raised the question of whether the project template code should keep living in compiler or move elsewhere. Linking it here because this sync is another concrete example of the maintenance cost we should discuss.