You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do we have applicative or monadic concatenation of list forms ? The current list form support mostly only seems to do mapping. I don't actually want to impose. Mostly I just want a confirmation I'm not missing something in the documentation.
I've found Ott very useful in formalizing my little logic programming language anyhow and I've wanted to drop by and thank the creators anyway.
Anyhow here's the problem case I've run into.
I have a little logic programming language and I made an original semantics in terms of which values satisfy a predicate (in a given environment.) See here.
However, after thinking about the issue I want to make a more explicit semantics of judgements stating precisely which "contexts" (relations) map to what lists of environments and matching terms.
If the previous approach was a little like the procedure denote then the new approach ought to be much more like search. We have explicit big step rules evaluating "contexts" into lists of normalized "terms" (values) that they match.
At first I thought list forms might work for my approach but it seems list comprehensions don't really work for joining over multiple sets of values. I came up with a little workaround of the merge rule but it's not so great for a variety of reasons.
I think what I would really like is some form of notation like </ Di ++ D'j |- Ni, N'j // i, j /> that gives me every possible combination here kind of like how applicative functors or monads work. But I'm not really sure of the fully scope of the problem.
Anyway thanks. I've already found Ott very useful for prototyping even if you can always add new features.
The text was updated successfully, but these errors were encountered:
Do we have applicative or monadic concatenation of list forms ? The current list form support mostly only seems to do mapping. I don't actually want to impose. Mostly I just want a confirmation I'm not missing something in the documentation.
I've found Ott very useful in formalizing my little logic programming language anyhow and I've wanted to drop by and thank the creators anyway.
Anyhow here's the problem case I've run into.
I have a little logic programming language and I made an original semantics in terms of which values satisfy a predicate (in a given environment.) See here.
However, after thinking about the issue I want to make a more explicit semantics of judgements stating precisely which "contexts" (relations) map to what lists of environments and matching terms.
If the previous approach was a little like the procedure denote then the new approach ought to be much more like search. We have explicit big step rules evaluating "contexts" into lists of normalized "terms" (values) that they match.
The prototype Ott code for the new approach is:
At first I thought list forms might work for my approach but it seems list comprehensions don't really work for joining over multiple sets of values. I came up with a little workaround of the merge rule but it's not so great for a variety of reasons.
I think what I would really like is some form of notation like
</ Di ++ D'j |- Ni, N'j // i, j />
that gives me every possible combination here kind of like how applicative functors or monads work. But I'm not really sure of the fully scope of the problem.Anyway thanks. I've already found Ott very useful for prototyping even if you can always add new features.
The text was updated successfully, but these errors were encountered: