-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
This is not currently how the compiler works. It sounds like what you want is implied bounds. See the rendered document for the proposed changes as it covers your question. Fortunately there seems to be some recent progress on the issue.
This is not currently how the compiler works. It sounds like what you want is implied bounds. See the rendered document for the proposed changes as it covers your question. Fortunately there seems to be some recent progress on the issue.
Usually you should follow this.
In theory and practice you can't get both, but ideally you would get the first direction: if Polonius accepts it, then undefined behavior wouldn't happen at runtime. However, Polonius doesn't check unsafe code (since raw pointers don't have lifetimes). Also, there are known discrepancies between what Stacked-Borrows considered undefined behavior and what rustc/llvm consider undefined behavior (I believe Stacked-Borrows is currently usually slightly more strict, by which I mean it says fewer programs are valid), so those would need to be addressed to make it fully standard. See e.g. this issue where there's a discussion of whether Stacked-Borrows is doing the right thing or not.
I've been having way too much fun with klask and clapv3: https://github.com/barafael/error-safari. It's a tiny gui application for exploring different ways to define and handle errors. Klask uses egui under the hood to generate a gui from clapv3 parsed CLI.