XVilka

THIS GIST WAS MOVED TO TERMSTANDARD/COLORS REPOSITORY.

PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!

o11c

Things that a test can be annotated with:

• XFAIL(cond): for tests that are known to be buggy.
• FLAKY(cond): for tests that have nondeterministic bugs that have not been hunted down.
• SKIP(cond): for tests not applicable to the current platform, that cannot be fixed by installing or configuring dependencies.
• MISSING(cond): for tests that can't run because of uninstalled or unconfigured dependencies.
• WIP: for tests you are implementing
• TIME(cpumin, cpumax, realmax): min/max computation expected for a test. Also real time added in case you sleep or something.

o11c

List of intended memory-management policies (note: the actual policies are below, after both kinds of modifiers):

structure modifiers:

• relative - own address is added to make effective pointer. Useful for realloc and memcpy, as well as shared memory.
• middle_pointer - actually points to the middle of an object, with a known way to find the start
  • note particularly how this interacts with subclasses. Possibly that should be the only way to create such a pointer? It isn't too crazy to synthesize a subclass just for the CowString trick ...
• (other arithmetic tricks possible: base+scale+offset, with each of these possibly hard-coded (which requires that there be multiple copies of some ownership policies! we can't just use an enum) or possibly embedded)
• (but what about "object is stored in a file too large to mmap" and such? Or should those only satisfy "ChunkyRandomIterator" concept?)