v1.0.23-alpha
github-actions
released this
25 Jan 20:22
·
799 commits
to main
since this release
Added
- aiken: New
--trace-level
option for thecheck
andbuild
commands to
allow chosing the verbosity level of traces amongst three levels: silent,
compact & verbose. @MicroProofs @KtorZ - aiken: New
--filter-traces
option for thecheck
andbuild
commands
to enable restricting traces with more granularity between user-defined
traces, compiler-generated traces or both. @MicroProofs @KtorZ. - aiken-lang: Most builtin errors are now caught and instead catched trace
errors are thrown. The exception is BLS primitives.
Fixed
- aiken-lang: Fix flat encoding and decoding of large integer values. @KtorZ
- aiken-lang: Traces should not have following expressions formatted into a
block. @rvcas - aiken-lang: Sequences should not be erased if the sole expression is an
assignment. @rvcas - aiken-lang: Should not be able to assign an assignment to an assignment.
@rvcas - aiken-lang: Should not be able to have an assignment in a logical op
chain. @rvcas - aiken: Ensures that test expected to fail that return
False
are
considered to pass & improve error reporting when they fail. @KtorZ - aiken-lang: Fix generic edge case involving tuples.
- aiken:
aiken new
now uses the current version for the github action. - aiken-lang: Using the head_list builtin on assoc lists now works.
- aiken-lang: Now using correct discard match for constructor field access.
- aiken-lang: The list_access_to_uplc now always returns a lambda wrapped
term even with only discards. This fixes an apply error being seen by a few
people.
Removed
- aiken: The options
--keep-traces
(on thebuild
command) and
--no-traces
(on thecheck
command) have been removed; superseded by the
new options. @MicroProofs @KtorZ
Tip
- If you've been using
aiken check --no-traces
, you can recover the old
behavior by doingaiken check --trace-level silent
. - If you've been using
aiken build --keep-traces
, you can recover the old
behavior by doingaiken build --trace-level verbose
.