zappolowski

This is caused by `simplify` not being tail recursive. As a quick workaround you could try is to increase (or even remove) the stack size limit (`ulimit`).

Interestingly, that looks quite similar to what I started to implement yesterday ```rust #[derive(Clone, Debug)] enum Kind { Binary, Integer(Option, Option), Continuous(Option, Option), } #[derive(Clone, Debug)] pub struct Variable {...

Does this mean you're planning to treat `Infeasible`, `Unbounded` and/or `Notsolved` the same way as failing to read/write files or executing the solver? Or did you mean using `Either` instead...

The first proposal would mix errors originating from actually trying to run the optimization (e.g. missing optimizer executable, unable to write either input or output files) with the infeasibility to...

I've kept the branch up to date and tests are still passing. As far as I can tell, the discussions are resolved.

I would consider using `-r 5` without having a notification with this ID an error. Citing from DNS again (Table 1. Notification Components): > Replaces ID An optional ID of...

From my POV, there are two ways of dealing with it: 1. just error out when no matching notification is found to be updated - the error reporting should be...

> What if all possible ids have been generated? I consider reaching MAXINT practically impossible. If you manage to send 1k notifications per second you'd still need about 50 days...

This is due how the file is parsed. ```yaml - echo "a bug with colon: a" ``` is considered a dictionary with key `echo "a bug with colon"` and value...

> Out of curiousity, without this, what error do you get? What distro / system are you running into an issue on? I'm on Arch, but I think the issue...