nissy-core - The "engine" of nissy, including the H48 optimal solver.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Cleanup, update documentation, fix examples	Sebastiano Tronto	2025-12-14	1	-2/+2
\|
*	Renamed UNIX build script to build.sh, added info to README.md related to ↵	Sebastiano Tronto	2025-08-12	1	-1/+1
\| \| \| \|	windows build
*	Small improvemen to python example	Sebastiano Tronto	2025-08-12	1	-5/+7
\|
*	Simplified name of Python module	Sebastiano Tronto	2025-08-11	1	-5/+6
\|
*	Small fixes	Sebastiano Tronto	2025-08-08	1	-2/+2
\|
*	Small rework of optimal vs maxsols	Sebastiano Tronto	2025-04-17	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	I wanted to make the "optimal" and "maxsolutions" options mutually exclusive, but in the end I decided there is value in keeping both (e.g. for specifying a limit to the number of solutions when asking for "all" optimal"). Now optimal cannot be negative anymore, for the same reason of maxsolutions. The interface user (shell, UI) will have to take care of handling this in a way that makes sense for the user. Usually this means setting the maximum number of solutions to UINT_MAX (or a similar very high number) when the user wants "all optimal".
*	Improved C++ API and added info to README	Sebastiano Tronto	2025-04-14	1	-0/+37