You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presuming the long-term goal is a full clone of LINQ in Rust, this crate would provide:
the linq! macro that provides the syntactic sugar
the LINQ API against generic collection interfaces
a concrete implementation that operates efficiently against the claimed performance characteristics of those collection interfaces (array/vec/linked list/dict/...)
perhaps an optimised implementation that specifically targets the standard collections directly.
Other generic collections would work, though almost certainly inefficiently, because their performance characteristics differ from the standard collections, otherwise, why would they be worth the effort of implementing?
I assume that implementing LINQ for SQL in Rust would be a distinct crate, which would provide a concrete implementation that would collect all the expressions (are macros magic enough to do that?) and serialise the query in SQL, presumably explicitly targeting a placeholder collection class identifying a table.
If so, adding specific (ie. efficient) support for a custom collection class would be something for a hypothetical 'linq-for-foo' crate that depends on this crate and the foo crate.
What do you think of extending this crate to support LINq for Crux Datalog Query language?
This is Crux Datalog client in Rust: https://github.com/naomijub/transistor.
This is Crux Docs: https://opencrux.com/docs#queries
The text was updated successfully, but these errors were encountered: