Chase Wilson

Let me elaborate on my thoughts a wee bit: For the enum thing, this'd be an entirely new declaration type, so it's distinct (visually) and doesn't break or even touch...

It may be awkward in the actual implementation, but I think basing the api off of an in-process model is the best route for having an api that feels good...

I don't think it matters, each instance has the same starting state and as long as timestamps are obeyed the state of all nodes will become consistent

> Why not introduce an extra input relation with a single record that represents program mode or any other metadata the transformer needs and pass this relation to the transformer....

Well, I opened it because *I* need the feature. Multiple of my projects involving ddlog are language-based ones that already have things like interners and arenas that are used throughout...

It's both, that one is for doing it in transformers and this one is for doing it in vanilla relations

If anyone's found a workaround, I'd really love to use it until the issue's fixed

> Pure functions in Prusti cannot have loops @fpoli Is this a viper-level limitation or just something that prusti hasn't implemented yet? Loops within pure functions would be *really* nice...

That's what I do currently, ddlog's output relations are combined into the [`DerivedFacts`](https://github.com/RDambrosio016/RSLint/blob/d70ccf1a31ed8b6a790d8f04519e62500fd14153/crates/rslint_scope/src/datalog.rs#L23-L26) struct [here](https://github.com/RDambrosio016/RSLint/blob/d70ccf1a31ed8b6a790d8f04519e62500fd14153/crates/rslint_scope/src/datalog.rs#L94-L120) which are then made into diagnostics [here](https://github.com/RDambrosio016/RSLint/blob/d70ccf1a31ed8b6a790d8f04519e62500fd14153/crates/rslint_scope/src/lib.rs#L44-L70), ddlog has no knowledge of diagnostics (although it...

@RDambrosio016 @Stupremee Can y'all fancy up the rule impls, I'm not sure how to make the actually emitted errors *good*