| Commit message (Collapse) | Author | Age | Lines | SHA |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
The old method of having functions for every parsing action of a
function definition produced messy results. We're replacing it with a
struct which will hold a wide assortment of parsed values. This makes
the interface much sleaker with only a minor increase in code.
The downside is a lot of data gets repeated, however since this struct
will only be used in macros, i.e. compile-time, that doesn't matter too
much.
|
| | |
|
| |
|
|
| |
anything
|
| | |
|
| | |
|
| |
|
|
| |
the line is too long
|
| |
|
|
|
| |
Types like HashMap<Key, Value>, i.e. with commas inside the angled
brackets
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
For example, in `Vec<...>`, `<` is Joint and before it would get
skipped.
|
| |
|
|
| |
Use it in multiple zkVMs, simplifying codebase
|
| |
|
|
| |
to items
|
| | |
|
| | |
|
| |
|
