[rust-dev] Patterns that'll never match

Kevin Cantu me at kevincantu.org
Thu Jun 5 21:20:21 PDT 2014


Could be an interesting library!

Kevin
On Jun 1, 2014 4:29 AM, "Matthieu Monrocq" <matthieu.monrocq at gmail.com>
wrote:

>
>
>
> 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
>> doing.
>>
>>
>> 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.
>
> -- Matthieu
>
>
>>
>> _______________________________________________
>> Rust-dev mailing list
>> Rust-dev at mozilla.org
>> https://mail.mozilla.org/listinfo/rust-dev
>>
>>
>
> _______________________________________________
> Rust-dev mailing list
> Rust-dev at mozilla.org
> https://mail.mozilla.org/listinfo/rust-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/rust-dev/attachments/20140605/27846b28/attachment.html>


More information about the Rust-dev mailing list