Enable "display" standard library function

[remo5000]

Features

• display and timed work
• Context now has a generic type that can be used to provide external properties, named externalContext. In this case, it is a WorkspaceLocation.

Issues fixed

• Fixed an issue with WorkspaceLocation enums (untracked as blocking PR not merged)

Caveat

• display and timed do not work unless redux-persist is turned off. This is related to redux-persist stores extra parts of the state #138 , where it attempts to stores the Context (when it is not supposed to), or something related to the workspace, and hence throw an error on trying to serialise an object with a circular structure. Once redux-persist stores extra parts of the state #138 is resolved, the functions will work.

[coveralls]

Pull Request Test Coverage Report for Build 115

• 11 of 18 (61.11%) changed or added relevant lines in 5 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.05%) to 30.371%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/slang/createContext.ts	4	5	80.0%
src/slang/stdlib/misc.ts	2	8	25.0%

Files with Coverage Reduction	New Missed Lines	%
src/slang/stdlib/misc.ts	1	39.02%

Totals
Change from base Build 113:	0.05%
Covered Lines:	1092
Relevant Lines:	3176

---

💛 - Coveralls

[ning-y]

Interpreter no longer evaluates asynchronously.

const f = (i) => i < 3 ? 0 : f(i-1) + f(i-2);

const delay = () => f(13);  // increase value for longer delay

function iter(i) {
    delay();
    display(i);
    return i === 0 ? 0 : iter(i-1);
}

iter(15);

[remo5000]

Interesting. The handleConsoleLog actions seem to run before the render method is called, causing the state to be correct but the stop button and display output not rendering till the very end. Really weird, good catch!

[remo5000]

I've confirmed this to be a bug present previously, even in the master branch. I've opened up an issue (#142).