-
Notifications
You must be signed in to change notification settings - Fork 1
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 Array Inference #23
Comments
This has further issues, as even code like (defcircuit array-from-data-check-consts ((output (array int 10)))
(def ((bar (to-array 36)))
(prld:+ (prld:check 5 (int 32))
(prld:get bar 0)))) causes issues, as we lack the size information in the hole slot. Due to this, we can't actually infer the array type, as when we recompute the array type, it will always be an unknown int type. If we had holes which had application, we could submit this back as an equation given the extra hole size in the |
mariari
added a commit
that referenced
this issue
May 30, 2022
See #23 for a type inferencing issues I've found
mariari
added a commit
that referenced
this issue
May 30, 2022
See #23 for a type inferencing issues I've found
mariari
added a commit
that referenced
this issue
Jun 5, 2022
See #23 for a type inferencing issues I've found
Merged
mariari
added a commit
that referenced
this issue
Jun 5, 2022
See #23 for a type inferencing issues I've found
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the advent of #22 I've left some holes, namely:
These holes make it so the user has to give the type of an array when allocating it. If we can omit that information, and get it here then we can have the type of the array be inferred (though length can not be).
The text was updated successfully, but these errors were encountered: