allow two-step compilation/evaluation #12

Activity

1. hardbyte commented on Aug 11, 2025

   

   hardbyte

   on Aug 11, 2025

   Owner

   More actions

   Yes I'm very open to that.

   I think upstream is likely to make changes to align closer to the cel-spec to have a binary go/proto serialization e.g. cel-rust/cel-rust#116
   Also see cel-rust/cel-rust#115

   Happy to review a PR otherwise I'll probably wait until upstream have made some changes.
2. hardbyte commented on Aug 19, 2026

   

   hardbyte

   on Aug 19, 2026 – with Claude

   Owner

   More actions

   This is implemented as of the cel-rust 0.14 work (#37) — cel.compile() returns a reusable Program, and the reference introspection asked for here is available too.

   Verified against main (bc21129, cel 0.14.3):

   import cel
   
   adult = cel.compile("person.age >= 18")
   adult.source                       # 'person.age >= 18'
   [adult.execute({"person": p}) for p in persons]
   
   prog = cel.compile("age(person)")
   prog.variables()                   # ['person']
   prog.functions()                   # ['age']
   prog.references()                  # {'variables': ['person'], 'functions': ['age']}

   Program.execute() accepts either a plain dict or a cel.Context, so the same compiled program can be run against many contexts, and variables()/references() give you the static analysis needed to narrow a DB query to the fields a filter expression actually touches.

   Static analysis notes: names bound by comprehension macros (the x in [1, 2].map(x, x * 2)) show up in variables() because they are identifiers in the AST, and functions() includes CEL operator overload identifiers (e.g. _+_) alongside named functions.

   Closing as completed — please reopen if the reference output doesn't fit your query-optimisation use case.

   ---

   Generated by Claude Code
3. hardbyte

   closed this as completedon Aug 19, 2026