Skip to content

Conversation

@MaxAtoms
Copy link
Collaborator

Closes #2027

@MaxAtoms MaxAtoms self-assigned this Nov 18, 2025
@MaxAtoms MaxAtoms added the project api Relates to flowR's main API label Nov 18, 2025
@MaxAtoms
Copy link
Collaborator Author

Just out of curiosity and because I was unsure: Is it okay that we always load the full built-in memory at these three call-sites, regardless of configuration?

image

@MaxAtoms MaxAtoms marked this pull request as ready for review November 19, 2025 14:44
@MaxAtoms MaxAtoms requested a review from EagleoutIce November 19, 2025 14:44
@MaxAtoms MaxAtoms requested a review from EagleoutIce November 20, 2025 16:26
Copy link
Member

@EagleoutIce EagleoutIce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Besides this,
we need new documentation for the context
(ref #2044)

EagleoutIce added a commit that referenced this pull request Nov 21, 2025
@MaxAtoms MaxAtoms requested a review from EagleoutIce November 25, 2025 17:45
*/
export function emptyGraph(idMap?: AstIdMap) {
return new DataflowGraphBuilder(idMap);
const ctx = new FlowrAnalyzerEnvironmentContext({ config: defaultConfigOptions } as FlowrAnalyzerContext);
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this approach okay considering that it is only code for test/documentation?

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

Labels

project api Relates to flowR's main API

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Project] Move built-in environment into the analyzer context

3 participants