acme-circular-containers VS conway

Compare acme-circular-containers vs conway and see what are their differences.

acme-circular-containers

Spineless containers which are fast to read but inefficient to update (by gelisam)

conway

Demonstrating comonad transformers. (by gelisam)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
acme-circular-containers conway
1 1
4 36
- -
0.0 0.0
about 3 years ago over 7 years ago
Haskell Haskell
LicenseRef-PublicDomain -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

acme-circular-containers

Posts with mentions or reviews of acme-circular-containers. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-02-20.
  • 2-Dimensional Algebraic Data Type
    2 projects | /r/haskell | 20 Feb 2021
    You could also have edges pointing up and left in addition to down and right... but then updating any cell would cost O(width*height), because we'd once again have to allocate an entire new array. See my acme-circular-containers package for more information about that kind of approach and why it is a bad idea.

conway

Posts with mentions or reviews of conway. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-02-20.
  • 2-Dimensional Algebraic Data Type
    2 projects | /r/haskell | 20 Feb 2021
    Now, while it's a bad idea to have a node-and-edges data structure with edges in both directions, it is, of course, nevertheless very useful to be able to navigate in both directions. The Comonad abstraction is very useful for modelling the topology of a data structure, that is, to model which cells are above, below, to the left, and to the right of each other. This abstraction isn't really a new way to represent the data (we can use any of the representations we've discussed above), it's a layer of information we can put on top of the data in order to navigate. My conway repo implements (...but does not really explain) such a 2D array in the context of Conway's Game of Life. I chose to have the array wrap around both horizontally and vertically, but you could also make the world stop at the boundary by giving a different Comonad instance. That's kind of the point: you write a Comonad instance to explain the topology of your structure, including whether it wraps around or not.

What are some alternatives?

When comparing acme-circular-containers and conway you can also consider the following projects:

acme-cofunctor - A Cofunctor is a structure from category theory dual to Functor

ascii-cows - ASCII 🐮s

acme-everything - Install everything.

typesafe-precure - Type-safe transformations and purifications of PreCures (Japanese battle heroine)

yes-precure5-command - Extended yes command to reproduce the phrases when the Japanese battle heroine PreCure transform.

acme-functors

acme-omitted - A name for omitted definitions

acme-one - The identity element and the absorbing element of Cabal package dependencies

acme-lolcat

acme-box - An empty Haskell project for testing purposes

acme-cutegirl - A package which exists solely to try and give the user a cute girl. Executable and library are both available.

acme-flipping-tables - Stop execution with rage.