-
Notifications
You must be signed in to change notification settings - Fork 23
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
Better support for projections in flux refinements #925
Comments
Is this mostly a parsing issue? i.e. are these things supported "internally" ? |
I'd need to look at the code again to be 100% sure but I don't think this is currently supported - the left side of "dot" expressions are parsed as an expr path and this is propagated through surface -> fhir. We would need to parse the left side as an expression and change the representation through surface and fhir. I don't think this is too bad though - I can take a stab at it. |
This is supported in rty and the encoding into fixpoint should handle it as well (modulo bugs arising because we've never tested it). We need to change the surface syntax and fhir, and consequently sort checking/elaboration. |
I think the parsing may be a pain here... 🙃 |
Something like this may work
I'm taking inspiration from edit: |
Right now, it seems like it's not possible to use projections in a few scenarios. Say I have the following structs:
This does not work:
And neither does this:
It would be helpful from an ergonomic standpoint if we could support this sort of thing.
The text was updated successfully, but these errors were encountered: