A comment on commenting systems, implementation discussion for your discussions on implementations.
about 12 minutes
So you've read over the Recursive Type Aliases hints in the Elm compiler documentation and that all seems straightforward.
Mainly because it is, but unfortunately simple examples like this are seldom actually useful when you need to actually do something.
In my last post, I talked about generating a nested structure of comments and any replies pulled from a database at the backend of oration, so that this data could be exposed via an API in JSON format.
Now, I'd like to continue the conversation at the frontend—hopefully answering the question: how do we invoke a recursive type and do some work with one?
I don't always use recursion; but when I do, I don't always use recursion.
about 4 minutes
SQL databases are still one of the best ways of storing relational data, but sometimes you hit a wall transferring your representation to or from a table based layout.
Say we have a table full of Foos, where some Foos may have other Foo parents.
This can easily be represented in a table with some unique primary key id, a secondary key parent, which joins to the parent's id, and whatever dataFoo may hold.
Retrieving this table into a rust data structure, we'd find ourselves with something like Vec<Foo>, where Foo is defined as
Make yourself a little nest of eggs. Where your eggs are perfectly round and magically float in free space.
about 5 minutes
So you want to do some sphere packing to make your inflatable space habitats for deployment on the Moon and Mars snug and cozy.
Perfectly straightforward you think to yourself; since one can start with a triplet of spheres tangent pairwise by placing one at some origin on a 2D plane, extending the second out in the \(x\) direction and completing the triangle by identifying the third sphere's position based on the radii of all three.