[rust-dev] Patterns that'll never match
matthieu.monrocq at gmail.com
Sun Jun 1 04:29:03 PDT 2014
On Sun, Jun 1, 2014 at 1:04 PM, Tommi <rusty.gates at icloud.com> wrote:
> On 2014-06-01, at 13:48, Gábor Lehel <glaebhoerl at gmail.com> wrote:
> It would be possible in theory to teach the compiler about e.g. the
> comparison operators on built-in integral types, which don't involve any
> user code. It would only be appropriate as a warning rather than an error
> due to the inherent incompleteness of the analysis and the arbitrariness of
> what things to include in it. No opinion about whether it would be worth
> Perhaps this kind of thing would be better suited for a separate tool that
> could (contrary to a compiler) run this and other kinds of heuristics
> without having to worry about blowing up compilation times.
This is typically the domain of either static analysis or runtime
instrumentation (branch coverage tools) in the arbitrary case, indeed.
> Rust-dev mailing list
> Rust-dev at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Rust-dev