Alex Engelberg

Since paths can now be compiled in-line, I would suggest instead writing a macro that can be used in-line for a specific field of a record. e.g. ``` (select [ALL...

This is fixed by #405 and has shipped in v0.1.7251. Also coming soon to Homebrew etc.

Reopening this issue so people can find it more easily. This is now fixed on the latest commit, but it's still broken in homebrew, because we can only bump the...

We fixed #363, but that fix didn't incorporate this feature request yet, so I'm re-opening this ticket.

Thanks, I definitely agree that's an issue with Loco at the moment. It'll require some thought to determine how to add enough validation to every constraint to prevent these types...

You're right, something seems off here. As an experiment I changed the boundaries of your `:sse` variable to [-25,25], to mimic what Loco is doing behind the scenes in your...

Other strategies are on the radar. Thanks for submitting. On Monday, November 9, 2015, Joshua Griffith [email protected] wrote: > Rather than always defaulting to minDom_LB, would it be possible to...

Exposing custom strategies through a Clojure interface would be tough, especially while keeping the Choco solve performant. A strategy is basically a function that takes an array of variables and...

Don't worry, you don't have a misunderstanding of how loco works... It's either a bug with $or, $mod, or $=, or there's something quirky about the Choco API that I...

Hi James, This is a [bug](https://github.com/chocoteam/choco3/issues/272) within Choco, so unfortunately it is beyond my control for now. The Choco [mod](https://github.com/chocoteam/choco3/blob/master/choco-solver/src/main/java/org/chocosolver/solver/constraints/IntConstraintFactory.java#L411) constraint is actually represented as an intricate composition of multiple...