Lack of organization #5
Assignees
Comments
alhassy
pushed a commit
that referenced
this issue
Aug 20, 2019
[X] Added a top-level link to this document from 700 github.io website.
[X] Added new menu item: A bare-bones presentation of a file, with 700-annotations
stripped out, is now provided.
[X] Moved prototype material into its own directory ---tackling issue #5.
[X] Included a comment in §2.9 addressing issue #10 to reduce ambiguity.
[X] Trying a different colour scheme for the exported HTML
---exporting in spacemacs-light theme.
[X] The meta-primitive is “:kind”, not “:type” which is an overloaded word.
The codebase and examples now refer to the former exclusively;
addersing issue #7.
[X] Added further docs to §2.5/2.6 to clarify that the main difference between
the two is that the former does things directly, whereas the latter uses
composition instead. This addresses issue #9.
[X] Issue #8 has been addressed. A new todo has been added:
→ Examples from the user-manual
should be exported into an Agda file which is then easily checked;
or the resulting generated code should be generated when export happens.
|
A new directory for the prototype has been created;; issue tackled in commit 449156d |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Everything is at the top-level, and not organized. Some stuff is obsolete, some isn't. It would be nice to use directories for organization, and a roadmap in the README to enable one to understand all the different artifacts available here.
The text was updated successfully, but these errors were encountered: