cfallin opened issue #3575:
Right now, the ISLE compiler prioritizes matching "more specific rules first" when building the decision trie that becomes the generated code.
This is somewhat intuitive, but also imprecise. The actual details depend on subtle workings of the trie construction. We should:
- Define a proper total ordering over all patterns, which can be understood independently of compiler implementation details and reasoned about intuitively; and
- Implement this in place of the current system.
alexcrichton labeled issue #3575:
Right now, the ISLE compiler prioritizes matching "more specific rules first" when building the decision trie that becomes the generated code.
This is somewhat intuitive, but also imprecise. The actual details depend on subtle workings of the trie construction. We should:
- Define a proper total ordering over all patterns, which can be understood independently of compiler implementation details and reasoned about intuitively; and
- Implement this in place of the current system.
github-actions[bot] commented on issue #3575:
Subscribe to Label Action
cc @cfallin, @fitzgen
<details>
This issue or pull request has been labeled: "isle"Thus the following users have been cc'd because of the following labels:
- cfallin: isle
- fitzgen: isle
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
cfallin labeled issue #3575:
Right now, the ISLE compiler prioritizes matching "more specific rules first" when building the decision trie that becomes the generated code.
This is somewhat intuitive, but also imprecise. The actual details depend on subtle workings of the trie construction. We should:
- Define a proper total ordering over all patterns, which can be understood independently of compiler implementation details and reasoned about intuitively; and
- Implement this in place of the current system.
Last updated: Nov 22 2024 at 16:03 UTC