f307e214c3
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.
A modern smart contract platform for Cardano
QuickStart
Prerequisites
For now you'll need rust installed, see rustup.
Getting started
In case you have fresh installation of rustup you might need to do:
rustup install stable
$ cargo install --git https://github.com/aiken-lang/aiken.git
$ aiken --help
Alternatively nix builds are available via flakes.
How to use
For more information please see the user manual.
Roadmap
Aiken defines its roadmap using Github Milestones. The roadmap isn't set in stone, but gives a high-level overview of where the project is headed for.
Contributing
Want to contribute? See CONTRIBUTING.md to know how.
Note
The name comes from Howard Aiken, an American physicist and a pioneer in computing.