Skip to content

Making samples readable #13

Description

@nobugs-hare

Depends on #39

'samples' MUST be end-user readable.

At the very least:

  • make file names reasonable
  • separate different implementations into separate files
  • clearly mark implementations which we RECOMMEND to the end-user (separate the rest into 'internal' folder)

Desired - is to make .cpp version THE SAME AS node.js one; maybe make two versions - with automated testing and without - BOTH in .js and .cpp

Activity

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions