kdl-script
kdl-script copied to clipboard
Gankra
Execute KDL files!
The syntax is stubbed out but I think the type checker just throws the info out. Also I should think through where/if bounds/duplicate checks should happen. I forget if C...
It might be useful to allow you to say something like: ```kdl pun "MyArray" { lang "rust" { struct "Elem" { x "u32" y "u32" } alias "MyArray" "[Elem; u32]"...
`Option` is an important Rust type for FFI, so we need to support it somehow. Easiest way would be to like, hardcode it as `?` and let you write `?&T`,...
It's a meme but it'd be cool if the meme worked for everything! This required building out a lot more initialization syntax, although we arguably want that anyway for power-users...
Everywhere you see `Spanned::from` I'm creating a garbage span `0..0` span. I do this a lot for the tydent sub-parser. One way to do this is passing extra context into...
Right now we do the normal thing of just returning Results and failing as soon as we hit an error. miette lets you have errors that contain multiple other errors...
kdl-rs says the world is i64/f64 but we want to support more than that (like i128/u128). But also a backend may have representation limitations. Ideally we should validate that numbers...
Positional idents/args/fields are written as `_` (or more usually `_ "MyType"`) and basically say "this is purely positional, I don't care about the name". I half-heartedly started on this and...
`@tag "u32"` should be something you can do on an `enum` to the effect of `repr(u32)` in rust for c-like enums (or `enum class Blah: uint32_t` in C++).
Strawman varargs syntax for saying there's varargs but that you want to test this particular set of values passed in them: ```kdl func "blah" { inputs { x "u32" "..."...