3 ms·
Thanks... that is what I thought. Honestly, like I mentioned, I don't see that as a particularly useful advantage. The thing is, there is no single line that m
by jmull 5y ago
Thanks... that is what I thought. Honestly, like I mentioned, I don't see that as a particularly useful advantage.
The thing is, there is no single line that makes a library suitable for my project, whether it's for a constrained environment or not. I carefully consider many aspects of a library, all from the perspective of what, specifically, my project needs. no_std might be one thing to look for, but I don't know that it's really answering that many of my questions. Also, in my embedded dabbling, there seem to be such an incredibly rich set of libraries available for constrained environments it is astounding. So the lack of no_std doesn't seem to be holding non-Rust back.
> In C you would have to either write everything yourself, read through all of your dependencies, or just cross your fingers.
I really don't think no_std changes that at all.
- brundolf 5y agoFair points. I wonder what it would look like to have multiple kinds of enforceable crate-level constraints so that everyone doesn't have to take or leave the same "single line"? > in my embedded dabbling, there seem to be such an incredibly rich set of libraries available for constrained environments it is astounding What about more general libraries that aren't specifically designed for embedded scenarios? It seems like being able to know up-front whether or not those, for example, allocate, would be helpful