exercism/common-lisp-analyzer

Common Lisp Analyzer

(c.f. For full details and up to date documentation on automated analyzers for Exercism see the Automated Analysis repository.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Interface

(.c.f. The Analyzer Interface)

The /opt/analyzer/bin/run.sh script that the docker image runs receives two parameters:

1. the test slug
2. the input directory namestring. This directory contains the submitted code.
3. the output directory namestring. This directory will be writable.

The script MUST write the following files to the directory:

2. analysis.json: The results of the analysis.

The output of the script MAY write the following files to the directory:

1. analysis.out: any information that may want to view later for debugging.

The script MAY produce output to stdout and stderr which will be persisted for later.

common-lisp-analyzer's Issues

The master branch will be renamed to main

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.

Does the analyzer actually analyze anything?

I've been looking at the analyzer code for a bit, and to my untrained eyes it looks like it doesn't really analyze anything yet. Is that correct? If it doesn't, I would suggest disabling the analyzer in the track config (https://github.com/exercism/common-lisp/blob/main/config.json#L9), as that will save us some resources.

Deploy Common Lisp representer

A placeholder issue to leave open until we have the representer deployed and working on new exercises.

TODO List:

• exercism/terraform#14
• #8

Update references to tooling-webserver.

The repositoriy and binary name have changed.

/c.f./ https://github.com/exercism/tooling-webserver/blob/master/README.md#installation-docker

Update interface

The defined interface has changed:

1. generate.sh is now run.sh
2. It takes 3 arguments: slug, input directory and output directory.

Stop using daewok common-lisp docker images

Use clfoundation images instead.

(cf. https://www.timmons.dev/posts/common-lisp-docker-images.html)

Add LICENSE file with AGPLv3 license

c.f. exercism/#5334

AGPLv3

Use `:keyword` instead of `#:keyword` for package symbols

To be consistent across all the code for the Common Lisp track let's use :keyword style rather than #:keyword style in defpackage and related expressions.

(ref: exercism/common-lisp#437)