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

Figure out why the CommRingSolver doesn't work in this case #1097

Closed
felixwellen opened this issue Feb 2, 2024 · 5 comments
Closed

Figure out why the CommRingSolver doesn't work in this case #1097

felixwellen opened this issue Feb 2, 2024 · 5 comments

Comments

@felixwellen
Copy link
Collaborator

felixwellen commented Feb 2, 2024

When looking at the goal type in the case below, it is actually something the CommRingSolver should be able to solve. But when trying to solve this, the solver actually gets meta-variables it cannot use.

comment
image

@felixwellen
Copy link
Collaborator Author

felixwellen commented Feb 2, 2024

Here is another case, which might be related (or not):

comment
image

@felixwellen felixwellen changed the title Figure out why the CommRingSolver doesn't in this case Figure out why the CommRingSolver doesn't work in this case Feb 4, 2024
@felixwellen
Copy link
Collaborator Author

When looking at the goal type in the case below, it is actually something the CommRingSolver should be able to solve. But when trying to solve this, the solver actually gets meta-variables it cannot use.

image

It seems like the marco gets only the type in the message below:
image
So the task is to figure out how to use the reflection interface to tell agda to get more information on the type of the hole.

@ncfavier
Copy link
Member

ncfavier commented Feb 6, 2024

Links are more useful than screenshots:
#1093 (comment)
#1093 (comment)

It looks like adding wait-for-type goal in solve!-macro does it.

@felixwellen
Copy link
Collaborator Author

Yes - it does! Many thanks!

@felixwellen
Copy link
Collaborator Author

#1093 is merged and solves both problems -> closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants