aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSebastiano Tronto <sebastiano@tronto.net>2022-06-01 11:50:15 +0200
committerSebastiano Tronto <sebastiano@tronto.net>2022-06-01 11:50:15 +0200
commit3fceaa8706b983ef5e81527e5ded3c62f0ba4c1d (patch)
tree5ac10771a9472d23d7f704d5231ec814c77faba7
parent7873731b0ddfad2da61b55d016a6c08806819167 (diff)
downloadnissy-3fceaa8706b983ef5e81527e5ded3c62f0ba4c1d.tar.gz
nissy-3fceaa8706b983ef5e81527e5ded3c62f0ba4c1d.zip
fixed readme strikethrough lines
-rw-r--r--README.md12
1 files changed, 0 insertions, 12 deletions
diff --git a/README.md b/README.md
index b79462c..891241e 100644
--- a/README.md
+++ b/README.md
@@ -86,18 +86,6 @@ vs composed) is work in progress.
86 86
87The two paragraphs below are not true anymore since version 2.1 (June 2022). 87The two paragraphs below are not true anymore since version 2.1 (June 2022).
88 88
89~~~There is one caveat: each coordinates also needs an inverse function that takes a~~~
90~~~coordinate value and returns a cube which has that coordinate. This is in general~~~
91~~~more complicated, but luckily the cube does not need to be fully built or consistent.~~~
92~~~This inverse-coordinate is used only in one specific step when generating symmetry~~~
93~~~data, and I don't know if it is possible to avoid it (maybe it is). It is also used~~~
94~~~when building pruning tables, but in that case it is avoidable.~~~
95
96~~~Note: this part is different from what Cube Explorer does. Overall I think it is~~~
97~~~conceptually easier, although in practice it was still hard to implement.~~~
98~~~If anything it is more generalizable and one can use it to build any coordinate~~~
99~~~they might like.~~~
100
101### Solving 89### Solving
102 90
103Solving is implemented as a generic function that takes both a step and 91Solving is implemented as a generic function that takes both a step and

Generated with cgit - Back to sebastiano.tronto.net