est.social

3 postitusega2 osalejaga0 postitust täna

Kat Marchán 🐈FINALLY got around to speccing out the new suffix type annotation feature for <a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a>: <a href="https://github.com/kdl-org/kdl/pull/513" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/kdl-org/kdl/pull/513</a> Commentary welcome! It's very exciting!I believe right now that the complexity cost, especially taking into account that there's a serviceable escape hatch, and fairly good ambiguity/typo protection, is well worth the value of people being able to write DSLs that use this feature.I am, by the way, mostly writing out the grammar/spec itself after a much longer discussion by a bunch of people who poked all sorts of holes in a silly idea I threw over the fence: <a href="https://github.com/kdl-org/kdl/issues/510" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/kdl-org/kdl/issues/510</a>I am immensely thankful to the KDL spec and implementer community for everything they do! We're really all making an amazing language here.

Hemera :nixos: :ms_snow_leopard:Some example testcase errors, thanks to the awesome <a href="https://meow.social/tags/miette" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#miette</a> crate from @zkat (who also authored <a href="https://meow.social/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a> btw!)

Hemera :nixos: :ms_snow_leopard:Alright!I just released a first functional version of a new crate: 🔧 <code>test-dsl</code> at 0.1.0🦀 <a href="https://github.com/TheNeikos/test-dsl/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/TheNeikos/test-dsl/</a>To paraphrase the readme: <code>test-dsl</code> allows you to easily author tests by decoupling between the 'test harness', 'verbs' and 'conditions'.It's role in your testing infra would be as boilerplate reduction, so that you can focus on just writing tests around the behaviour of your system. I'm using this pattern for example in a client-server context. So I have verbs like <code>start_server 1</code>, <code>start_client 2</code>, <code>connect_client 2 1</code> etc...Of course the meaning of these verbs is highly project-specific.If a verb does fail, either by panicking or returning an error, you get a nice error output telling you exactly which file and which verb caused the error. Allowing you to more easily pin-point directly what went wrong, rather than potentially searching through a log.It works great together with <code>datatest-stable</code> from the <code>nextest</code> project, but it works just as fine standalone.It uses <a href="https://meow.social/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a> as the language to write your testcases in, so its fairly nice to read.It's still missing more comprehensive documentation, but as a prototype it should work just fine! It actually sprung out from having used this pattern a few times, and I didn't want to re-write the boilerplate around it, and maybe re-use some code between projects.<a href="https://meow.social/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a> <a href="https://meow.social/tags/rustlang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rustlang</a>

Kat Marchán 🐈GitHub is now officially highlighting <a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a> docs!! On the app, too!

Kat Marchán 🐈Realistically, would <a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a> being officially standardized by one of the major international standards organizations influence your interest and/or ability to use KDL, especially at work?

Kat Marchán 🐈There is a proposal for <a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a> to extend it such that you can have things like <code>10%</code> or <code>20px</code> and have that mostly Just Work in terms of existing KDL featuresBut, t’s not as perfectly clean as I would’ve liked, and so I’m hoping others (you?) will help 👀 for other issues<a href="https://github.com/kdl-org/kdl/issues/510" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/kdl-org/kdl/issues/510</a>

Kat Marchán 🐈lol turns out that when you base a language on xml/s-exp and you give it a really lightweight syntax, it just kinda turns into a really really nice DSL format <a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a>I think that might be what actually sets apart node-based formats from JSON-semantic “map and array” formats. It’s much less convoluted, usually, to make the former look and feel like an executable language

Kat Marchán 🐈<a href="https://github.com/kdl-org/kdl/issues/510" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/kdl-org/kdl/issues/510</a> what do y’all think of this? I know I promised not to change stuff anymore but it’s… a reasonable ask, and I think this might be an elegant solution? <a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a>

SlatianIs someone already working on a rust adapter that implements <a href="https://github.com/kdl-org/kdl/blob/main/JSON-IN-KDL.md" rel="nofollow noopener noreferrer" target="_blank">json-in-kdl</a> to serde compatibility?<a class="hashtag" href="https://pleroma.envs.net/tag/kdl" rel="nofollow noopener noreferrer" target="_blank">#kdl</a> cc: <a class="u-url mention" href="https://toot.cat/@zkat" rel="nofollow noopener noreferrer" target="_blank">@zkat</a>

Kat Marchán 🐈I should probably figure out a way to put this on the site but honestly, it's not the cutesy+professional vibe <a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a> is really trying to give off so maybe I'll just post it here and be done with it.

Kat Marchán 🐈how do y'all feel about this hypothetical <code>package.kdl</code>?<a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a>

Kat Marchán 🐈what if.... Rust macro for a mostly <a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a> syntax so you can just do:<pre><code>kdl! { foo 1 2 3 bar { hey key=val #true; there! } } </code></pre>

Kat Marchán 🐈<a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a> dedented multiline strings are absolutely incredible. I don't know how I've managed to survive in languages that don't have this feature. I'm using the heckin out of it

Kat Marchán 🐈Oh god I think we’re gonna have to do a new edition of <a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a> with a fairly impactful change. But I want it so bad. It’s so good. And there’s a few other minor tweaks we’ve been wanting to pop in there too, for certain corner cases.Perhaps a new process: <a href="https://github.com/kdl-org/kdl/discussions/496" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/kdl-org/kdl/discussions/496</a>Thoughts?

Kat Marchán 🐈I just had the most ridiculous idea for enabling <code>/</code> in plain <a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a> identifiers.Quick, someone talk some sense into me: <a href="https://github.com/kdl-org/kdl/discussions/494" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/kdl-org/kdl/discussions/494</a>

Kat Marchán 🐈So I had an idea last night: What if there was a way to define, in <a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a> Schema, an LSP SemanticTokens mapping such that kdl-lsp could provide custom syntax highlighting for your KDL-based DSLs?So for example, the following KDL would be highlighted such that “class” and “@“ would be highlighted with your editor theme “keyword” color, “Foo” with your theme “class” color, <code>"hello"</code> as “documentation”, and <code>name</code> as “property”, and <code>string</code> as “type”?<pre><code>class Foo { @ hello name string } </code></pre>There’s some limitations as to how far you would be able to take this without your own LSP server, but it would probably take you pretty far.

Kat Marchán 🐈Another cool project using <a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a>!This one is a neat little programming language using KDL for its package manifest. Literally what it was created to do!<a href="https://onyxlang.io/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://onyxlang.io/</a>

Kat Marchán 🐈Heh. At first I thought it would be kinda silly to start the KDL Schema spec by using it to author its own schema……but actually it’s been really helpful and the schema is getting more and more clean as I iterate on it. I’ve even learned a few tricks I just hadn’t thought about before that only really work in a language like <a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a>.

Kat Marchán 🐈gawd, I've been drafting big, complicated <a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a> docs recently, refactoring and editing them, just full-on restructuring everything as I go along.Just like... grab the whole scope. shove it somewhere else. done. And when authoring, I don't feel like I'm constantly having to type "structural chars"And it is really nice. Like, this has been a genuinely smooth experience compared to the constant delimiter-tweaking of JSON, or the Absolutely Bananas nonsense that is YAML semantic indentation (WHY).When authoring, JSON/XML have a very low signal:noise ratio. YAML opts for cognitive overhead.To poke holes in my own thing: the main "cognitive overhead" I seem to be running into is the classic XML "should this be an attribute/property or a child?" for key/value stuff. They both have pros/cons, incl doing bothThe other difficulty is the node thing, since KDL doesn't map to arr/obj/scalar

Kat Marchán 🐈27 pages! By contrast, the JSON RFC is 16. Honestly that’s not bad at all, considering how barebones JSON is. YAML is… 80. 😬<a href="https://toot.cat/tags/KDL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDL</a>

Viimatised otsingud

Otsimisvalikud

Administraator:

Serveri statistika:

#kdl