Szabolcs Horvát
Szabolcs Horvát
@GroteGnoom The last thing that's missing here is `constraint`. You've been working on this: does it behave with multi-edges and self-loops?
Thanks @GroteGnoom! Do you think we can close this now, or are there any other functions to verify?
I added these two to the top.
Yes, it would be nice to have a set of nested messages / statuses. It also applies to the status handler (instead of progress handler). I can see a front...
Another idea here is to do away with the status handler completely (`igraph_status`) and use only the progress handler. If a function cannot provide progress information, only a status, it...
> IMHO the status handler is redundant; we can simply have progress handlers where the status of each task may be "indeterminate", and this effectively replicates the functionality of the...
> If we decide to get rid of the status handler completely, I'd keep `IGRAPH_STATUSF` anyway as a shorthand notation for reporting progress for an item with an indeterminate progress....
This sort of use is replaceable with `IGRAPH_PROGRESS` with a clear message + NaN value (assuming a future design that handles NaN).
_Generally_ Sage is very good, so if they didn't find a better way, I think we can go ahead. It's always good to leave a comment in the code pointing...
Sounds good. Just letting you know that there are a number of outstanding PRs from people working on other projects, so it may take a while before we get the...