volution / vonuvoli-scheme Goto Github PK

From this issue we have spawn #91

Tasks

• implement key hashing;
• implement "load-or-build" functions;
• implement expiration marker;
• implement integrity hash;
• implement cache cleaning of all namespaces;
• implement cache pruning of expired values;
• implement cache pruning if out-of-space;
• implement "default" values for various cache-open arguments; (i.e. #f -- no-set; #t -- default, x -- that value;)
• add time-to-live argument to select, include, and related;
• implement caching of opened LMDB databases corresponding to previously used namespaces;
• implement "keyed" caches (used as cache buster or additional axis in addition to namespaces);
• implement "cache busting" based on a "token", per individual select, include, and related builtins; (this could be used to implement something similar to E-Tag HTTP header;)

Tasks

• implement *_regex_match_position (and related) builtins;

Tasks

• implement functional composition that allows for multiple values as inputs / outputs;
• fix implementation of apply; (check R7RS specification;)
• implement the following function call builtins (and related):
  • call-with-list;
  • call-with-vector;
  • call-with-values; (part of R7RS;)

Tasks

• implement support for regular expressions;
• implement support for uniques;
• add flag to accept only values that can be read back (i.e. accepted by the current parser, and compliant with the serialization library);

Tasks

• enhance macro to add tracking facility;
• enhance macro to fail in release mode if tracking information is not filled;
• update code to use tracking facility;

One can use the following regular expression to search places eligible for issue tracking:

(fail|failed)(|_unimplemented|_unreachable|_panic|_or_panic)!

Tasks

• implement support for bytes values as proper path components;
• implement temporary file creation;

Dependencies

• #20 -- ports to std::io::Read and std::io::Write adapters;

The following snippet should return 0 not 5!

(display
    (let ((l '()))
        (do ((i 0 (+ i 1))) ((= i 5) (l))
            (when (zero? i) (set! l (lambda () i)))))
)

Tasks

• fail_panic, panic_0, and all related;
• TODO;
• FIXME;

Tasks

• identify appropriate continuous integration solutions (that are free, work with Rust nightly, and integrate with Github);
• choose one of the continuous integration solutions;
• configure the chosen continuous integration solution;

Tasks

• implement ranged bytes writing builtins;
• update ranged bytes writing primitives;
• update tests;

Tasks

• implement macro;
• convert TODO and FIXME comments to macro usage;

Tasks

• implement ranged string writing builtins;
• update ranged string writing primitives;
• update tests;

Tasks

• identify how the current parser can be used to read values;
• TBD;

Well... This is never going to happen, but one needs to aim high (in order to be disappointed)... :)

However, as silly as this objective might seem, the main reason this project was created, was to enable systems scripting (and systems programming) in a language saner than Bash, easier to work with than C, and easier to deploy than Python / Ruby.

It might happen that Scheme is not the perfect language for anyone, but it does provide a modern alternative...

It is absolutely certain this issue will always remain open to remind the developers what is one of the main project goals!

Tasks

• implement integer-based hashing (SipHash and SeaHash);
• implement cryptographic hashing (Blake2b and Blake2s);
• implement both seeded (explicitly or randomly) and unseeded variants;
• implement primitive procedures to expose builtins;

Tasks

• string regular expressions;
• bytes regular expressions;
• parameters;
• parameter;
• promise;
• opaque;

Tasks

• list iteration;
• comparisons;
• value display (in std::fmt::Display and std::fmt::Debug);
• value writing (in ports);
• value serialization;
• value hashing;
• compilation;

Tasks

• update compiler to support while and until;
• update compiler to support while-cond and until-cond;
• update compiler to support do-cond;
• update optimizer to handle an cond (or if or equivalent) for the break statement; (this is not semantically equivalent)

Tasks

• characters;
• strings;
• bytes;
• symbols;
• keywords;
• paths;