research: Prolog frontend on Prologos post-elaboration IR#56
Draft
kumavis wants to merge 1 commit into
Draft
Conversation
Stage 1 research note categorizing standard Prolog features into compatible-as-is vs small/medium/large additional work to land them on Prologos's existing relational IR (expr-defr / expr-clause / goal-desc) and BSP-LE propagator runtime. Headline finding: ~95% of Datalog-fragment Prolog and ~70% of ISO-7 Prolog map directly onto existing IR; the residual gap is concentrated in dynamic features (assert/retract, attributed vars, CHR) which are paradigm-level mismatches against CALM-monotone propagator semantics and naturally co-evolve with the PReduce series. Includes architectural caveats (tabling default, fork-not-stack, closed goal-kind set), four-stage staging proposal, and open questions on cut semantics, side-effect ordering, and marketing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stage 1 research note categorizing standard Prolog features into
compatible-as-is vs small/medium/large additional work to land them
on Prologos's existing relational IR (expr-defr / expr-clause /
goal-desc) and BSP-LE propagator runtime.
Headline finding: ~95% of Datalog-fragment Prolog and ~70% of ISO-7
Prolog map directly onto existing IR; the residual gap is concentrated
in dynamic features (assert/retract, attributed vars, CHR) which are
paradigm-level mismatches against CALM-monotone propagator semantics
and naturally co-evolve with the PReduce series.
Includes architectural caveats (tabling default, fork-not-stack,
closed goal-kind set), four-stage staging proposal, and open
questions on cut semantics, side-effect ordering, and marketing.