René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Using code-generation to generate ","articleBody":"I have made some breaking API changes on my branch. This is a WIP, but I'm showing early to get feedback early.\n\nhttps://github.com/nkallen/nodegit/commit/458e08079a8089ba9a75f5046fc4d2b173164f3e\n\nI'm investigating code generation instead of manually writing bindings libgit2. This branch code-gen's an easy class, `GitOid`, from a JSON description of the libgit2 interface. The JSON is based on the data from here, http://libgit2.github.com/libgit2/v0.18.0.json, but highly modified\n\nIN THEORY you just mark methods as \"async\", \"prototype\", \"constructor\", etc. and it will \"just work\". It works for `GitOid`, all tests pass.\n\nThe new interface for the raw `Oid` is what I described:\n\n```\nvar oid = git.raw.Oid.fromString(\"SHA1\")\noid.sha() = ...\n```\n\nThis API change has repercussions, changing some APIs to sync from async, as in `Commit`. ATM, the API is inconsistent, as `Reference`'s `sha()` method is still async, because of indirect references. However, I propose to change the api to have have an `IndirectReference` class and a `DirectReference` class, with `IndirectReference` only having a `resolve()` method, and `sha()` being synchronous on DirectReference.\n\nIt is no longer possible to construct a raw `Oid` from scratch, as it would be in an invalid state; and further objects are now immutable.\n\nAlong the way I've identified what I believe to be memory leaks. I'm hoping to have the code-gen produce code without these leaks, if they are indeed real.\n","author":{"url":"https://github.com/nkallen","@type":"Person","name":"nkallen"},"datePublished":"2013-06-19T22:27:45.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":34},"url":"https://github.com/70/nodegit/issues/70"}