Follow-up for #37 (comment)

Currently, our .nimble file contains:

which means that we will execute arbitrary code if

• nimscripter or docopt are re-tagged
• or any dependency of nimscripter ( assume, balls, grok, ups, npeg, sync) or docopt (regex, unicodedb) receive a new release.

Ideally, we'd use a Nimble lock file. The current Nim stable release (1.6.6) supports the Nimble version that supports lock files, but does not yet ship with such a Nimble.

The .nimble files of our Nimble dependencies:

• https://github.com/beef331/nimscripter/blob/0105cfc7d825/nimscripter.nimble
• https://github.com/disruptek/assume/blob/c7eeee5aec63/assume.nimble
• https://github.com/disruptek/balls/blob/52a17872d42e/balls.nimble
• https://github.com/disruptek/grok/blob/4b8963fd9a71/grok.nimble
• https://github.com/disruptek/ups/blob/afd93b80bd8c/ups.nimble
• https://github.com/zevv/npeg/blob/a480df260659/npeg.nimble
• https://github.com/planetis-m/sync/blob/9b8c29262863/sync.nimble
• https://github.com/docopt/docopt.nim/blob/65da8739a753/docopt.nimble
• https://github.com/nitely/nim-regex/blob/b10d4b87dae0/regex.nimble
• https://github.com/nitely/nim-unicodedb/blob/675407fa4b6e/unicodedb.nimble

For example: https://github.com/exercism/nim-representer/runs/8007649732

As of now, the proposed representation for Nim proc/func/template/macro calls is to normalize them all to regular calls. For example:

`+` 1, 2 => `+`(1, 2)
1 + 2    => `+`(1, 2)
-1       => `-`(1)

Is this the desired result?
Certain call styles are more idiomatic

In line with our new org-wide policy, the master branch of this repo will be renamed to main. All open PRs will be automatically repointed.

GitHub will show you a notification about this when you look at this repo after renaming:

In case it doesn't, this is the command it suggests:

git branch -m master main
git fetch origin
git branch -u origin/main main

You may like to update the primary branch on your forks too, which you can do under Settings->Branches and clicking the pencil icon on the right-hand-side under Default Branch:

We will post a comment below when this is done. We expect it to happen within the next 12 hours.

The expected tree output should start on the next line being as they are stripped anyways

Unclear whether tuples will be interpreted Correctly

Follow-up for #37 (comment)

Low priority. The dependencies of docopt are all pure Nim, so docopt won't make it harder to deploy a statically linked representer binary in a container that has no Nim or glibc.