John Howard

Nice! I ended up playing around with this on my flight and took a slightly different approach. What I ran into was that there was no way to have things...

The main question for me is if we want to allow turning an opaque value into something. I am not actually 100% sure how this works in Go, what happens...

Note https://github.com/cel-rust/cel-rust/pull/96 is a prior attempt at this. I am not 100% sure why the need for the unsafe stuff

Did a bit of playing around to make defining functions more ergonomic: https://github.com/howardjohn/cel-rust/blob/b0c90986b6d75f29b2976b850af9ffa0b7534f13/cel/src/functionsx.rs#L60-L74 Then my functions can just be like ```rust impl IpAddr { pub fn is_localhost(self: Arc) -> Result...

I don't have a strong opinion on many of the discussion points but would say that overall this PR, as is, unblocks some things for me (at first, implementing a...

LOG_FORMAT=json env var will do this. Could be better documented certainly

What about something like: ```rust let ctx = Context::default().with_regex().with_time().with_string() ``` Or ```rust let ctx = Context::default().add_function_set(functions::strings()) ``` Where `add_function_set` accepts a trait that just has `fn add_functions(&mut Context)`. Then we...

No, just a HTTPRoute filter or policy. Like https://istio.io/latest/docs/reference/config/networking/virtual-service/#HTTPFaultInjection, for example. Then users or tooling can utilize that to build a holistic chaos engineering strategy

Also its not 100% clear in the spec but I think you can only have 1 `*` and it must be the first element if so?

One thing ambiguous in the current spec is if a the following are valid: - `foo*bar.com` - `*.foo.*.com` - `foo.*.com` I assume no and you can only have exactly 1...