David Wong
David Wong
I learned about https://pest.rs/ today
I also asked bard to produce a grammar file considering an example X) maybe that's a good way ```python WHITESPACE = _{ " " | "\t" | "\n" | "\r"...
Yeah I wanted to avoid that if possible so I reverted back to latest stable. I'm wondering why it's a complicated issue to fix now :o (as it was successfully...
I just implemented this for another project here: https://github.com/o1-labs/proof-systems/blob/mimoo/snarky2/kimchi/snarky-deriver/src/lib.rs#L509 if this can help. Basically the strategy was to look at all the fields of the struct, collect their types in...
breaking it up, the ILL seems to come from the last function call in here: ``rust let state = &mut state.as_mut().0; let constraint = constraint.as_ref(); if let Some(cs) = &mut...
trying to debug print the CamlFVar here gives me a different signal: "Command got signal SEGV." (and now a "Command got signal ABRT.", I'm collecting them all!)
what's the status here, can we merge this?
Can you label this as easy/medium/hard? Can we provide more info and ask the open source community to take a look at it?
to add to this, I don't think we should support expressions for now! but we should make sure that any types are supported though if that's not already the case
mmm interesting, wondering if that means that "constant" shouldn't be in the type