SetReplace
SetReplace copied to clipboard
C++/Wolfram Language package for exploring set and graph rewriting systems
I get this when running `./lint.sh`:  Changing `which` to `command -v` fixes the issue. _Originally posted by @daneelsan in https://github.com/maxitg/SetReplace/issues/596#issuecomment-761087458_
### The problem Due to tests parallelization #578, we are now downloading the docker image with Mathematica 4 times, which is redundant. We should figure out how to only download...
There currently exist multiple global variables serving the purpose of documentation, and listing available options/properties/etc. for various functions, such as `$WolframModelProperties`, `$SetReplaceMethods`, etc. The better way is to put this...
### The problem In addition to the Markdown linter which would check the formatting/spacing/empty lines in Markdown, we can have an English linter, which is going to spot issues with...
Currently, `HypergraphPlot` always uses `"SpringElectricalEmbedding"` for the underlying 2-edges graph layout. It would be useful to allow arbitrary layout, although that won't extend to `RulePlot` as easily because not all...
### The problem Wolfram Language formatting should be included in the `./lint.sh` script and run in the git hooks and CI. ### Possible solution There are two candidates I am...
Linter
The code consistency is currently somewhat out of whack. Tabs and spaces are used inconsistently, indentation is different, the line width is not enforced, etc. We need a linter that...
Requires #579. ### The problem We currently build and test Wolfram Language code in the same Circle CI job, which results in awkward behavior such as artifacts being uploaded 4...
Requires #335. ### The problem The eventual goal is to reproduce all `MultiwaySystem` functionality using the local multiway system. As a start, we need to implement the `"StatesGraph"` property for...
### The problem We currently run all tests for all changes to the code. This is, however, not always necessary. Each test depends on certain parts of the code, and...