Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

effects: replaces usages of ALWAYS_FALSE with TRISTATE_UNKNOWN #44808

Merged
merged 1 commit into from
Apr 1, 2022
Merged

effects: replaces usages of ALWAYS_FALSE with TRISTATE_UNKNOWN #44808

merged 1 commit into from
Apr 1, 2022

Commits on Mar 31, 2022

  1. effects: replaces usages of ALWAYS_FALSE with TRISTATE_UNKNOWN 

    Although they are basically equivalent in the current implementation,
it would be more correct conceptually if we propagate `TRISTATE_UNKNOWN`
instead of `ALWAYS_TRUE`, as it is hard or impossible to derive a global
conclusion from a local analysis on each statement in most places.

This commit also adds a docstring that simply explains the design of the
effect analysis.
    @aviatesk
    aviatesk committed Mar 31, 2022
    Configuration menu
    Copy the full SHA
    8806ebd View commit details
    Browse the repository at this point in the history