slint/internal
Olivier Goffart a2d5ddaeca Fix priority of aliases when default value are involved
This code would have unpredictable results:

```slint
export Button := Rectangle {
    property<bool> the_enabled <=> touch.enabled;
    property<bool> the_visible <=> touch.visible;
    background: !the_enabled ? blue : red;
    border-color: !the_visible ? green : yellow;
    border-width: 15px;
    touch := TouchArea {}
    fs := FocusScope {
        enabled <=> root.the_enabled;
        visible <=> root.the_visible;
    }
}

Demo := Rectangle {
    VerticalLayout {
        spacing: 10px;
        Button { the_enabled: false; the_visible: false; }
        Button { the_enabled: false; the_visible: false; }
        Button { the_enabled: false; the_visible: false; }
        Button { the_enabled: false; the_visible: false; }
        Button { the_enabled: false; the_visible: false; }
        Button { the_enabled: false; the_visible: false; }
        Button { the_enabled: false; the_visible: false; }
    }
}
```

Because the enabled and visible property defaults to true (default
enforced by the compiler), but we set it also to false via an alias
2022-05-09 09:30:01 +02:00
..
backends GL backend: fix locating the default font in slightly atypical environments 2022-05-07 21:59:16 +08:00
common Bump version number to 0.2.3 2022-05-04 12:32:58 +00:00
compiler Fix priority of aliases when default value are involved 2022-05-09 09:30:01 +02:00
core Refactor the Model tracking in a module (#1223) 2022-05-05 10:25:15 +02:00
core-macros Bump version number to 0.2.3 2022-05-04 12:32:58 +00:00
interpreter Bump version number to 0.2.3 2022-05-04 12:32:58 +00:00