Thanks for your input! I’ll have a look at both build flags and macros for sure! For my specific problem enums will do just fine I guess, but having an overview about the possibilities helps a lot!
Thanks for your input! I’ll have a look at both build flags and macros for sure! For my specific problem enums will do just fine I guess, but having an overview about the possibilities helps a lot!
Thanks for your reply!
Thanks for the advice! I didn’t know generic functions were preferred. But it makes perfect sense if you think about it.
Thanks for the explanation! I think just using an enum will do perfectly well in my case.
Beware they started charging for the database tools even if you own an all-products license (the plugin was included in the EAP version).
IntelliJ still has it bundled iirc.
https://plugins.jetbrains.com/plugin/10925-database-tools-and-sql-for-webstorm--rustrover
Edit: Deleted because I mixed up two different products lol.
I still think they could make federation an opt-in preference though.
Yeah so effectively not federated. Pretty sure they’re not actually interested in federating anyway
That makes sense, thanks again! I think dynamic dispatch is not as much of a performance issue in my case, yet you’re totally right not to waste resources that aren’t actually needed. Keeping things on the stack if possible is also a good thing.
I’ll definitely need to read more about Rusts type system but your explanation was already very helpful! I think this might be why my initial approach felt unnatural - it works but is quite cumbersome and with generics there seems to be a more elegant approach.