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

Abstract over the specific Constraint.t type used by the backing constraint system #859

Merged
merged 10 commits into from
Jan 7, 2025

Conversation

mrmr1993
Copy link
Member

@mrmr1993 mrmr1993 commented Jan 6, 2025

This PR builds on #858, delivering on a large part of the promise of previous iterations: this allows us to define a constraint-system-specific constraint enum instead of overloading the snarky one. In particular, this gives the ability to have safe rust FFI types for constraint system generation, by only allowing the specific constraints that it supports.

As part of the pre-work that built up to this, we have also ensured that a Typ.t for any particular constraint definition is compatible with only the constraint systems that support it, ensuring that we get better type safety for OCaml / JS too.

@dannywillems
Copy link
Member

Changing the base branch to master. It seems it is not doing automatically. GH having some issues?

@dannywillems dannywillems changed the base branch from feature/abstract-run-state to master January 7, 2025 11:03
@dannywillems dannywillems self-requested a review January 7, 2025 11:06
@@ -64,22 +64,15 @@ module type S = sig
module Constraint : sig
type t = (Cvar.t, Field.t) Constraint.t [@@deriving sexp]

type 'k with_constraint_args = ?label:string -> 'k
val boolean : Cvar.t -> t
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I thought we were using it everywhere in Pickles.

@dannywillems
Copy link
Member

Context clearer now. We want to avoid mixing constraints from different backends too.

@dannywillems dannywillems merged commit 36c1add into master Jan 7, 2025
3 checks passed
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

Successfully merging this pull request may close these issues.

2 participants