You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have evaluate2(<project>, <sourceId>) and spice it with function call error location. Wrap existing code with error location modifiers corresponding to their parse nodes. Reducer: Return the locations of runtime errors #763.
To summarize again my suggested small task list is
Unit test for typeCheckArguments to show how it can replace the switch statement
Add any type
Provide the new interface // 3 dayish
Provide bindings backdoor and remove partials // 1 dayish
remove call keyword // 0.5 dayish.
-- milestone
Go on typing // 5 dayish
-- milestone
errors // 2-3 dayish
-- milestone
memoization //2-3 dayish
Highlights of the new interface:
evaluate(project, sourceId). Text is not evaluated it; instead identified source in a project is evaluated. To keep the tests around without changing I will provide a back compatible evaluate(which creates an on the fly single source project) but bindings will be gone.
getBindings(project, sourceId). Backdoor for bindings of a piece of source code. Partial concept and passing bindings will be gone. The code will work on continuations. Bindings are supplied for debugging only not for execution continuation.
chainTo(project, source1, source2). Make source2 a continuation of source1. This replaces continuing with bindings.
Later the project will be enhanced for errors and memorization
getMemoizationTable(project)
As everything has to be evaluated with a sourceId, all errors will have full location like in normal compilers.
Just to keep my short term priorities visible<
** Urgent **
Short term Issues:
evaluate2(<project>, <sourceId>)
and spice it with function call error location. Wrap existing code with error location modifiers corresponding to their parse nodes. Reducer: Return the locations of runtime errors #763.Unscheduled
Waiting for
Background:
Epic: Modules #835 // Modules Epic (background)
Modules, pros, cons #842
ReducerProject handles file imports. Keep an eye on Simple file import system #711
https://github.com/quantified-uncertainty/squiggle/milestone/6
Squiggle to TypeScript conversion. Intensive memory and speed loss, infinite loops #980
Reducer Project - API Revamp #968 ReducerProject pull epic-reducer-project
Conflict with Slava Proposal: unifying modules, records and code blocks #1012
Resolved Agreed-upon proposal for imports #1028
The text was updated successfully, but these errors were encountered: