diff options
author | William Carroll <wpcarro@gmail.com> | 2020-12-12T01·32+0000 |
---|---|---|
committer | William Carroll <wpcarro@gmail.com> | 2020-12-12T01·32+0000 |
commit | ee96a818e104cad7c60947a905d0799c4dc13905 (patch) | |
tree | 56f3c581874a59904e40a103a4f20be4300d95d6 /assessments/semiprimes/README.md | |
parent | ab732202808e175eb6ae670687280b8f4dbaf1e8 (diff) |
Define Server.semiprime
- Clear the boilerplate that `mix` generated - Consume `Math.factor` to test which inputs are semiprimes - Cache all inputs that are semiprimes as soon as we discover that they are - semiprimes I considered a couple things related to the Cache: - Could save space by storing all semiprime factors in a tree. This would make the lookups more expensive. Also because the tree's depth would never exceed two (because all semiprimes only have two factors), the tree would be quite broad, and we may not be saving enough space for the trade to be worthwhile. I might be wrong about that though. - We could consider pre-computing all semiprimes when we start the app, but without running some tests firsts, I'm not sure whether or not it's worth the trouble.
Diffstat (limited to 'assessments/semiprimes/README.md')
0 files changed, 0 insertions, 0 deletions