You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Much as we have split out WhereClause (Rust surface level) from the logic layer's notion of goals/clauses, we should split out Rust types that user's write from the surface layer. This shows up in #22 because e.g. fn types like fn(_, &'a T) -> &'static T should have some notion of implied bounds.
The text was updated successfully, but these errors were encountered:
Started on this in the user-ty branch. I'm currently just adding a (user-ty ...) function that converts types "in place", might be nicer eventually to move into the grammar.
Now that #56 added user-ty, I think the next step would be to modify the decl layer and the WhereClause to actually just use UserTy instead of Ty, and then do the (user-ty ...) invocations in the various decl metafunctions as well as where-clause->goal and friends. I'm going to hold off on doing that but it would make the code examples much nicer.
Much as we have split out
WhereClause
(Rust surface level) from the logic layer's notion of goals/clauses, we should split out Rust types that user's write from the surface layer. This shows up in #22 because e.g. fn types likefn(_, &'a T) -> &'static T
should have some notion of implied bounds.The text was updated successfully, but these errors were encountered: