Update Certifier-Show branch #6522
Open
Conversation
This file contains 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
* syntax: remove unnesessary parens * HasBlueprintSchema and HasBlueprintDefinition instances * Describe changes in the CHANGELOG * remove unnecessary -Wno-orphans
It should be "Note that deposit is mandatory".
) The documentation incorrectly asserted that a script can be used to require that certain transactions are provided for registration of the associated staking credential. That will be the case in the next era after Conway when `staking_registration` is deprecated, but as it stands currently, any staking credential (even those that contain a script hash) can be registered without any witness and thus it is not currently possible to enforce that a script must be executed in the transaction for registration to succeed.
Bumps [JamesIves/github-pages-deploy-action](https://github.com/jamesives/github-pages-deploy-action) from 4.6.3 to 4.6.4. - [Release notes](https://github.com/jamesives/github-pages-deploy-action/releases) - [Commits](JamesIves/github-pages-deploy-action@v4.6.3...v4.6.4) --- updated-dependencies: - dependency-name: JamesIves/github-pages-deploy-action dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…6433) Bumps [slackapi/slack-github-action](https://github.com/slackapi/slack-github-action) from 1.26.0 to 1.27.0. - [Release notes](https://github.com/slackapi/slack-github-action/releases) - [Commits](slackapi/slack-github-action@v1.26.0...v1.27.0) --- updated-dependencies: - dependency-name: slackapi/slack-github-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
This simply swaps around two type variables and two constructors, affecting `EvaluationError` and `EvaluationException`. Structural errors correspond to type errors and operational errors correspond to runtime errors, hence the former "precede" the latter. This PR finally reflects that perceived ordering. It's not really important, but I've got things mixed up before due to the previously counter-intuitive ordering, so I thought it'd be worth fixing it, given how easy that is.
Co-authored-by: Nikolaos Bezirgiannis <[email protected]>
* WIP * WIP * Extra tests for replicateByte and rotateByte * Extra tests for replicateByte and rotateByte * Extra tests for shiftByteString * Extra tests for countSetBits * Extra tests for findFirstSetBit * Disable failing test * Disable failing test * Extra conformance tests for readBit * Disable failing test * Extra conformance tests for writeBits * Remove some trailing spaces * Deduplicate trailing bytes in and/or/xor tests * Tell haskell-steppable-conformance about failing test
Co-authored-by: Nikolaos Bezirgiannis <[email protected]>
* Put the TOTAL line for a benchmakr comparison in a table of its own * Try again * Complete merge
Co-authored-by: Nikolaos Bezirgiannis <[email protected]>
This removes uniques from some golden test files, because those add a lot of noise in unrelated PRs.
…a structural error (#6443) Test that evaluation of a well-typed term doesn't fail with a structural error In theory, this is supposed to conclude the investigation on the "runtime type system" for UPLC. In practice unfortunately, PIR generators aren't very helpful here as per the recent Slack discussion (I'll reflect that in some GitHub issue later), plus the compiler being too slow doesn't help either. So this PR is more of a proof of concept than an actually helpful test, but better than nothing I suppose. Resolves #6150.
This replaces all occurrences of NOINLINE with the more reliable OPAQUE. Resolves #6269.
* WIP * WIP * WIP * WIP * WIP * WIP - Most of the nFD->FD proof is done but I am now wondering if the application rules need the force in them... * Some progress on the FD->pureFD proof... Not completely sure it is going in a good direction... * Made the parameters to istranslation implicit, since they are encoded in the relation anyway * WIP * WIP * WIP - with crazy variable binding issues * Add 'forall DecEq' to 'Relation' * Roman's additions. * Workign Float-Delay translation relation and decision procedure. * Missed a definition * Now uses Purity, althought that is 'stub code' at the moment. * Now with added Purity... * Remove 'Terminating' from 'translation?' --------- Co-authored-by: effectfully <[email protected]>
… be more complex? (#6513) * This seems 'too easy' but to certify things I don't think it needs to be more complex? * Er, I think this was the wrong way round * Add version select to haddock index page (#6499) * Remove plutus-ghc-stub (#6514) * Remove the Plutus Platform page (#6506) * Make the auction example end-to-end (#6477) * Mark `&&` and `||` OPAQUE (#6510) * Translation relation and decision procedure for the Float-Delay (#6482) * WIP * WIP * WIP * WIP * WIP * WIP - Most of the nFD->FD proof is done but I am now wondering if the application rules need the force in them... * Some progress on the FD->pureFD proof... Not completely sure it is going in a good direction... * Made the parameters to istranslation implicit, since they are encoded in the relation anyway * WIP * WIP * WIP - with crazy variable binding issues * Add 'forall DecEq' to 'Relation' * Roman's additions. * Workign Float-Delay translation relation and decision procedure. * Missed a definition * Now uses Purity, althought that is 'stub code' at the moment. * Now with added Purity... * Remove 'Terminating' from 'translation?' --------- Co-authored-by: effectfully <[email protected]> * WIP * Now with fake purity... * Some WIP from the other branch that is needed here. * Tidy some Agda... * Agda... --------- Co-authored-by: zeme-wana <[email protected]> Co-authored-by: Ziyang Liu <[email protected]> Co-authored-by: effectfully <[email protected]>
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.
Pre-submit checklist: