Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improving the import & export format of unary relations #558

Open
Laschoking opened this issue Dec 5, 2024 · 2 comments
Open

Improving the import & export format of unary relations #558

Laschoking opened this issue Dec 5, 2024 · 2 comments
Labels
Parser Rule-Parser-Related Issue
Milestone

Comments

@Laschoking
Copy link
Collaborator

The format attribute requires a tuple. As a special case, if only one type is given the pending , could be left out for simplicity.
@import Test :- tsv{resource="Test.tsv",format=(string,)
proposed:
@import Test :- tsv{resource="Test.tsv",format=(string)

@github-project-automation github-project-automation bot moved this to Todo in nemo Dec 5, 2024
@monsterkrampe monsterkrampe added the Parser Rule-Parser-Related Issue label Dec 5, 2024
@monsterkrampe monsterkrampe added this to the Release 0.7.0 milestone Dec 5, 2024
@matzemathics
Copy link
Collaborator

As far as I can see, there are two options:

  • accept (expr) as syntax for one-tuples -- this will require further consideration, probably we want something along the lines of "only interpret (expr) it as a tuple, if it is not sub-expression of another expression"
  • accept non-tuples in the format argument

The first one seems harder to implement, but also cleaner conceptually. I might give it a shot.

@matzemathics
Copy link
Collaborator

After examining the code and thinking about it some more, it seems hard to find a consistent rule, how to handle unary tuples. Maybe the second option is simply more consistent.

@aannleax aannleax modified the milestones: Release 0.7.0, Release 0.8.0 Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Parser Rule-Parser-Related Issue
Projects
Status: Todo
Development

No branches or pull requests

4 participants