Kasey White
665a8dec67
feat: add support for unconstr_data
...
-Builitins IR now acts like Record IR in terms of argument consumption
-UnConstrData returns as Pair(Data,Data) to conform with how pairs are treated behind the scenes.
2023-02-26 00:13:38 -05:00
KtorZ
81e072a14e
Add new acceptance test scenario: 064
...
- Type mismatch expected 'data' got 'integer'
- Type mismatch expected 'data' got 'list data'
2023-02-26 00:13:38 -05:00
Matthias Benkort
dc001c3745
Merge pull request #403 from aiken-lang/patch/cargo.nix
...
Update Cargo.nix
2023-02-24 08:36:54 +01:00
rvcas
48a221d09c
[create-pull-request] automated change
2023-02-24 02:28:39 +00:00
waalge
031507bea2
nix fmt
2023-02-23 21:26:38 -05:00
waalge
079017d24c
make default devshell allow for actual devving
2023-02-23 21:26:38 -05:00
waalge
5d984d7ee4
added workspace devshell
2023-02-23 21:26:38 -05:00
rvcas
98cd51db7c
feat: switch how output is saved
2023-02-23 21:26:11 -05:00
rvcas
7e153ef5d7
feat: adjust ci
2023-02-23 20:46:29 -05:00
rvcas
780a2a5d4f
feat: adjust ci
2023-02-23 20:37:09 -05:00
rvcas
ad85cf3ecc
feat: adjust ci
2023-02-23 20:22:39 -05:00
rvcas
7bc0514488
feat: adjust ci
2023-02-23 20:20:32 -05:00
rvcas
9792b193a3
feat: adjust ci
2023-02-23 20:03:09 -05:00
rvcas
06be109930
feat: adjust ci
2023-02-23 19:51:52 -05:00
rvcas
621626e8fa
feat: adjust ci
2023-02-23 19:47:57 -05:00
rvcas
7724da9af2
feat: adjust ci
2023-02-23 19:24:44 -05:00
rvcas
0066cc61cc
Release 0.0.29
...
aiken@0.0.29
aiken-lang@0.0.29
aiken-lsp@0.0.29
aiken-project@0.0.29
uplc@0.0.29
Generated by cargo-workspaces
2023-02-23 19:04:18 -05:00
rvcas
1bc3362788
feat: new release job and some release notes
2023-02-23 18:52:56 -05:00
rvcas
34afa9197c
chore: yeet bonnie
2023-02-23 17:21:10 -05:00
KtorZ
de3baa638e
[create-pull-request] automated change
2023-02-22 17:21:37 -05:00
KtorZ
539ed2dea4
Fix unicode char parsing in comments.
2023-02-22 17:33:13 +01:00
KtorZ
fbf65de1dc
Update default cost models for Aiken
...
Closes #396
2023-02-22 17:03:48 +01:00
KtorZ
bdee5e7995
Use variable-length threshold for levenshtein distance
...
Fixes #348
2023-02-22 13:29:39 +01:00
KtorZ
00e9dabe82
Add missing Plutus builtins to Aiken's lang.
2023-02-22 12:53:03 +01:00
KtorZ
0838d48f7c
Move module name validation outside of type-checking
...
And disable it for documentation generation. This way, we can generate documentation for aiken/builtins and aiken (prelude)
2023-02-22 11:51:32 +01:00
KtorZ
6465af3ae2
Add missing keywords to highlightjs for doc generation.
2023-02-22 11:50:31 +01:00
KtorZ
c0230a811f
Add 'plutusVersion' to blueprints.
2023-02-21 15:37:35 +01:00
KtorZ
82a32a082b
Remove 'purpose' from blueprint's schema.
...
This has been removed from the CIP-0057 specification since validators
are often re-used for multiple purposes (especially validators with
arity 2). It's misleading to assign a validator a purpose since the
purpose distinction actually happens _within_ the validator itself.
2023-02-21 15:30:41 +01:00
KtorZ
db0dfbbec1
Fix blueprint schema for tuples.
2023-02-21 15:29:33 +01:00
rvcas
e611d1ee7a
chore(cmd::new): update validator definition in generated readme
2023-02-20 15:51:12 -05:00
rvcas
97f03e5e98
fix: variants no longer exist
2023-02-20 15:46:55 -05:00
rvcas
94ffc36442
chore: cargo fmt fix
2023-02-20 15:46:55 -05:00
rvcas
bd93ced647
feat: improve validator arity check
...
* add count to dynamically adjust message
* check if args is greater than 3
* delete unused project level errors
2023-02-20 15:46:55 -05:00
rvcas
700e47d482
[create-pull-request] automated change
2023-02-20 15:33:03 -05:00
rvcas
6af6607df4
chore: github made a weird commit
2023-02-20 15:30:25 -05:00
rvcas
8b9991fd5b
chore: update some strings
2023-02-20 15:30:25 -05:00
Lucas
4b296de27c
Update crates/aiken-lsp/src/utils.rs
...
Co-authored-by: Matthias Benkort <5680256+KtorZ@users.noreply.github.com >
2023-02-20 15:30:25 -05:00
rvcas
52bb0e749e
fix(lsp): cannot blindly run publish after handle_request
2023-02-20 15:30:25 -05:00
rvcas
a8829889e3
feat(lsp): properly recompile project is files change
2023-02-20 15:30:25 -05:00
rvcas
c033cab79e
feat(lsp): bring over some stuff for completions, it basically doesn't work right though
2023-02-20 15:30:25 -05:00
rvcas
02eaefce21
feat(lsp): include docs on hover
2023-02-20 15:30:25 -05:00
rvcas
815d7d80c6
feat(lsp): hover and goto definition
2023-02-20 15:30:25 -05:00
rvcas
39ea803fe6
chore: remove eprintln
2023-02-20 15:30:25 -05:00
rvcas
38bcbaf701
feat(lsp): enable compiling a project
2023-02-20 15:30:25 -05:00
rvcas
b55726c90f
feat(project): remove Error::List and use Vec<Error>
2023-02-20 15:30:25 -05:00
Kasey White
70164282f8
fix: switch from unwrap to if let to allow boolean when
...
fix: test 67 fixed to take in ByteArray instead of string literal
2023-02-20 04:37:33 -05:00
Kasey White
2394438a91
clippy fix
2023-02-20 02:46:46 -05:00
Kasey White
87eb4ca3b4
feat: handle single constr when with multiple branches
...
Add case to acceptance test 40
Add special case for top level single constr in a when.
2023-02-20 02:46:46 -05:00
Matthias Benkort
95fce14b75
Merge pull request #391 from aiken-lang/string-and-bytearray-literals-iteration
...
String and bytearray literals iteration
2023-02-19 10:38:05 +01:00
KtorZ
f307e214c3
Remove parse error on bytearray literals for trace, todo & error, parse as String instead.
...
This has been bothering me and the more I thought of it the more I
disliked the idea of a warning. The rationale being that in this very
context, there's absolutely no ambiguity. So it is only frustrating
that the parser is even able to make the exact suggestion of what
should be fixed, but still fails.
I can imagine it is going to be very common for people to type:
```
trace "foo"
```
...yet terribly frustrating if they have to remember each time that
this should actually be a string. Because of the `trace`, `todo` and
`error` keywords, we know exactly the surrounding context and what to
expect here. So we can work it nicely.
However, the formatter will re-format it to:
```
trace @"foo"
```
Just for the sake of remaining consistent with the type-system. This
way, we still only manipulate `String` in the AST, but we conveniently
parse a double-quote utf-8 literal when coupled with one of the
specific keywords.
I believe that's the best of both worlds.
2023-02-19 10:10:42 +01:00
