linqbox VS chiselstrike

Positioning the Ark parser as a unified string syntax for runtime types (to me at least) makes the rationales and justifications for string parsing much more apparent and focused, much more so than just saying "hey, here's a library to write your types with strings just because". It also services as a prototypal implementation of what JS types "could" look like one day (if only we could drop the `scope` and `type` and just write the types naturally in JavaScript), I took a similar approach with https://github.com/sinclairzx81/linqbox many years ago.

Well, I wrote this ... https://github.com/sinclairzx81/linqbox, an actual LINQ syntax mostly for cartesian products (because cartesians with lambda are quite awkward after all)

One shouldn't need to look OData query syntax. For a C# client querying an OData endpoint, one simply need only write LINQ. A problem that exists in current fashionable languages is they do not support anything resembling LINQ. (Although some options exist for Elixir (Ecto) and Rust (implemented via proceedural macro). As for JavaScript....I have tried https://github.com/sinclairzx81/linqbox

If you ask me, TypeScript is a legitimate successor to C#. The only stuff missing in TypeScript is LINQ (as you mentioned) which is why I wrote this, and System.Reflection which is why I wrote this.

Thanks for the response. Here's a fun library I wrote https://github.com/sinclairzx81/linqbox

I got into the private Beta program of the new ChiselStrike product - Turso, an edge-hosted distributed database based on libSQL - the open-source and open-contribution fork of SQLite. Turso is hosted using Fly.io, meaning you have 26 regions of choice when it comes to deploying it.

It's here if that helps: https://github.com/chiselstrike/chiselstrike/tree/main/docusaurus/docs

If you mean the compiler implementation code, you can find it here. And if you mean TypeScript examples, here's one.