ecf4592be1
Pass in interner and data types map into decision tree builder
2024-11-01 19:34:47 -04:00
64f7886b23
Finished up creating the decision tree for lists. Only constr left.
2024-11-01 19:34:47 -04:00
b340de2cfd
Incremental commit for dealing with list tails
2024-11-01 19:34:47 -04:00
ca161d8a68
Continue work on handling lists with tails pattern matching
2024-11-01 19:34:46 -04:00
def268d966
Now working for all kinds of patterns except for constr
2024-11-01 19:34:46 -04:00
9369cbc1a3
Remove some warnings
2024-11-01 19:34:46 -04:00
43e859f1ba
Rework Decision Trees to use path to find the subject to test
2024-11-01 19:34:46 -04:00
20385a7ecd
Handle tuples and pairs properly now
2024-11-01 19:34:45 -04:00
97ee1a8ba6
Start working on using a decision tree for when expr. Also fmt fix. Other Stuff
2024-11-01 19:34:45 -04:00
2489e0fdd0
Fix aiken docs constant generation
...
Fixes #1048 .
2024-10-29 14:15:31 +01:00
2b7ca0e4a1
Avoid unsafe unwrap of line_numbers, gracefully handle non-existing matches
...
Fixes #1044 .
2024-10-25 11:37:50 +02:00
93d0191489
Fix latest clippy warnings.
2024-10-25 11:27:28 +02:00
e97fe332b1
Rename --filter_traces to --trace_filter
...
It has somehow always annoyed me that we have --trace_level (with 'trace' first) and --filter_traces (with traces, plural and last). Given that these two options are almost always used together, the inconsistency is frustrating.
2024-10-25 11:08:05 +02:00
8e90a933c6
Add better METAVAR info to some command-line flags.
2024-10-25 11:04:46 +02:00
7c4e044423
Rename --blueprint-input to --in
...
The context is indeed sufficient as pointed by @nemo83; no need to make the cli needlessly verbose.
2024-10-25 11:04:46 +02:00
f42cd83f10
Merge pull request #1047 from aiken-lang/riley/update-changelog
...
Updated Changelog
2024-10-25 10:42:53 +02:00
ab39eb82ce
Updated changelog again, forgot to put my name
2024-10-24 14:31:48 -07:00
413932d86b
Updated Changelog
2024-10-24 11:47:34 -07:00
8d8f91b76e
Add blueprint file input as option for blueprint apply
2024-10-24 14:01:48 -04:00
a7741ec286
chore: Release
2024-10-19 13:45:54 -04:00
3e076dd895
Update changelog for 1.1.5
2024-10-19 13:44:22 -04:00
b3e6c3ab6b
Fill-in CHANGELOG.
2024-10-19 11:04:18 +02:00
b04bb40532
Merge branch 'integer-to-bytearray-cost-fix'
2024-10-19 11:03:37 +02:00
365b3bf5bf
Remove dead-code and clarify note.
2024-10-19 11:00:46 +02:00
7f13fca1a4
Revert "Add acceptance tests #114 "
...
This reverts commit a18af83786
2024-10-19 10:52:37 +02:00
4b95db4f88
Fix data-type reification from Void
2024-10-19 10:50:44 +02:00
523b270a8f
Adjust telemetry output log.
2024-10-19 10:40:30 +02:00
53685dd1d5
Update cost model to properly calculate integer_to_bytearray
...
Also fix conformance tests to match plutus
2024-10-18 13:07:51 -04:00
9dd3ead3df
IntegerToByteString takes in the second param itself
2024-10-17 20:01:01 -04:00
a18af83786
Add acceptance tests #114
...
Demonstrate what seems to be the creation of an infinite recursion in the produced UPLC.
2024-10-13 13:40:25 +02:00
5fd349f571
Remove an unused opcode
2024-10-08 20:32:56 -04:00
5d4b3e69b9
Revert "Start working on using a decision tree for when expr. Also fmt fix"
...
This reverts commit e8f74985d5
2024-10-08 13:33:05 -04:00
e8f74985d5
Start working on using a decision tree for when expr. Also fmt fix
2024-10-08 13:30:29 -04:00
c7ae161a39
Mention quirks about gnu/musl linux artifact in the release guidelines.
2024-10-02 12:08:01 +02:00
79d0e45099
Don't mark openssl dependencies as optional on musl.
2024-10-02 11:32:17 +02:00
f4dbe1624a
Use target_os = linux instead.
2024-10-02 10:59:50 +02:00
19fe1d37e7
Make bundling of ssl conditionned by target environment instead of feature flag.
2024-10-02 10:51:21 +02:00
b0cad2bf1d
Update cargo-dist to v0.22.1
...
Necessary to make use of the custom github build steps.
2024-10-02 10:27:00 +02:00
5204831bac
Fix superfluous toml key in Cargo.toml.
2024-10-02 10:14:27 +02:00
538181f145
Move custom musl build instructions under generic cargo-dist configs.
2024-10-02 10:12:18 +02:00
31819fe197
Define custom build setup for musl target.
2024-10-02 10:05:39 +02:00
356d845a9a
chore: Release
2024-10-01 16:14:25 -04:00
e4e8ca8a6d
Update changelog
2024-10-01 16:13:33 -04:00
c8731c98c7
Remove prints
2024-10-01 16:09:44 -04:00
5fe6e3f77b
Finish simplification changes
2024-10-01 15:57:54 -04:00
c6c5cddead
Fix ordering of params on standard functions
2024-10-01 13:32:27 -04:00
2bbc699a25
Refactor some code to make a define_const AirTree function
2024-10-01 13:32:27 -04:00
513ca27717
Generate empty redeemer for `else` handler, to keep full compliance with the blueprint spec
2024-10-01 19:03:34 +02:00
e8d97028ad
Prevent constant evaluating to generic/unbound functions
...
Constants are like tiny programs, so they are bound by the same rules
as validators and other programs. In fact, functions are slightly more
flexible in that they allow generic constant expressions like
`List<a>`.
Yet, there is no way to contain such generic structure that contain
inhabitants in a way that satisfies the type-checker. In the example
of `List<a>`, the only inhabitant of that type that we can construct
is the empty list. Anything else would require holding onto some
generic value.
In addition, we can't force literal values into generic annotation, as
something like:
```
const foo: List<a> = [1, 2, 3]
```
wouldn't type-check either since the right-side would unify to
`List<Int>`. And again, the only right-hand side that can type-check
is the empty list without any inhabitant.
The added restriction on generic function is necessary because while
we allow constants to return lambda, we cannot (easily) generate UPLC
that is generic in its argument. By the time we generate UPLC, the
underlying types have to be known.
2024-10-01 18:37:40 +02:00
51b6b77db8
Build LSP projects with verbose tracing level
...
Without that, the language server might trigger awkward warnings about
unused imports due to trace stripping. So it's better to compile/check
projects in the language server in the most expanded form.
2024-10-01 16:12:41 +02:00
microproofs