3 ms·
Our two projects actually look like they have very different goals and approaches: I’m aiming for a rigorous solution for small design problems, like needing to
by kd5bjo 6y ago
Our two projects actually look like they have very different goals and approaches: I’m aiming for a rigorous solution for small design problems, like needing to add an index to a datastructure that wasn’t designed for one— nothing really to do with databases proper. I need the overhead for these simple cases to be low, so I’m trying to do as much as I can at compile-time inside the type system.
You’re doing everything at runtime (at least in Rust), which is a more flexible approach but can’t do things like trigger a compile error when attempting to access a field that isn’t present in a record.
- mamcx 6y ago> Our two projects actually look like they have very different goals and approaches Surely! but learning that is pretty interesting and could help, also, I think that combining ideas/crates is what give more power to the rust ecosystem... More to the point, I'm still thinking how/which data-structures to use, and how deal with the ability to provide SELECT/WHERE/etc across them (like a file) > nothing really to do with databases proper This is a big misunderstanding with the relational model: That is only for (r)dbms and storage. I'm looking to apply it to regular programming. Is similar to apply OO or Array or Functional paradigm as your base for a lang.