Skip to content

Conversation

@inaimathi
Copy link
Contributor

This is a more elaborate default-template that

  1. Includes separate src and test directories
  2. Includes a shell script that runs the test suite in sbcl
  3. Includes a .travis.yml file that allows the project to be trivially built in CI

I'm mainly submitting this because of inaimathi/house@262ceba#r45065608 (which tells me that it might be a good idea in general to standardize project structure because there are non-obvious ways to mess it up).

The points of contention I can see are related to the default choices (Should we use prove? Should we use travis? Should we assume sbcl?).

Overall:

  1. The defaults can be overriden as always (that was the point of the default-template addition :p)
  2. encouraging and simplifying testing/CI is worth picking reasonable but somewhat arbitrary defaults
  3. A plurality of the CL community seems to use sbcl in any case

#!/bin/bash
sbcl \
--eval '(ql:quickload (list :(#| TMPL_VAR name |#) :(#| TMPL_VAR name |#)/test))' \
--eval '(or (and (prove:run :(#| TMPL_VAR name |#)/test) (uiop:quit 0)) (uiop:quit -1))'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a specific runner. Maybe it could be another template directory?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants