intent of koka-community/koka-community submodules

[mccraigmccraig]

Question probably for @TimWhiting about the intent of koka-community/koka-community submodules

I have a JSON serializer I wanted to add (it's the code in this directory), but I'm not sure where to put it - is the intent of the submodules approach to koka-community/koka-community that there should be a wide list of top-level package submodules (e.g. koka-community/koka-community/serjson, or that there should be a relatively small list of submodules with wider lists of packages in the levels below (e.g. koka-community/koka-community/parsing/parsers/serjson) ?

[TimWhiting]

It's ultimately up to you. While the apis are still in flux / we are experimenting with different ways of parsing, I kind of hoped that we would put all related solutions together so that we could compare / benchmark them. So in that sense I would put it in parsers/serjson either directly or as a submodule (I think most people probably would prefer only having to deal with submodules for the koka-community repo though). If the API is rather finished, and you want to use it as a package having that name and also don't want the parsers import prefix, then I am fine with having it as a top-level package. But at that point we probably also want to add it as a submodule in the parsers for comparison purposes and add an extra include path to that subdirectory so that the module names line up.

[mccraigmccraig]

cool, thanks @TimWhiting , that gives me some understanding of what you were intending... I don't think it's finished yet, so I'll put it in parsers/serjson for now and live with the prefix on the import path, and then when I'm happier with it move it up to the top-level