51 get examples of custom rules

[deemp]

Closes #51

Links:

• original BNFC grammar
• use cases
• specifications

---

PR-Codex overview

This PR enhances the specifications.yaml file by defining MetaBinding patterns and functions for manipulating bindings.

Detailed summary

• Defined MetaBinding patterns for matching bindings
• Added functions for manipulating bindings like $replace and $combine

The following files were skipped due to too many changes: user-defined-functions/use-cases.yaml

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[fizruk]

I do not think we should work with strings. We should work with AST. <prefix> should be a valid $\varphi$-term and <suffix> should be a valid attribute (or chain of dispatch/application).

Also naming is not explained. Why mt?

[fizruk]

And also, why do we need $mt if we can simply use dot .?

[deemp]

I do not think we should work with strings.

Yes, it should be a dispatch.

Also naming is not explained. Why mt?

IDK. It comes from use cases. I'd prefer $dot.

And also, why do we need $mt if we can simply use dot?

I believe we shouldn't use dot with functions, should we? Which option looks better?

1. a.$name(b)
2. $dot(a, $name(b))

[fizruk]

Why do we need it if we have ?a for the name already?

[deemp]

We may not have the name in case of \?A ?a..b -> c

[deemp]

Also, we can use $name to extract all names from a list of bindings.
We may need to do that when we need to check that a name of some binding doesn't belong to that list.

[deemp]

Closing because this PR was split into #259 and #258.