[R-Forge #2183] Change j=list(xout=eval(...))'s eval to eval within scope of DT

Open
#628 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
r
Domain
data

Research direction

Start with the linked Stack Overflow discussion and R-Forge tracker entry to understand the requested evaluation scope for j=list(xout=eval(...)). Trace the existing data.table query construction and datatable.optimize path. Done means the evaluation behavior is defined and the chosen approach works within the DT query without breaking optimization.

Written by the indexing model from the issue text.

Description

feature request programming

Submitted by: Matt Dowle; Assigned to: Nobody; R-Forge link

As highlighted here :
http://stackoverflow.com/questions/11872499/create-an-expression-from-a-function-for-data-table-to-eval

Or, advise to construct and eval the whole DT query (provide compact way to do so easily), to play nicely with datatable.optimize.

Dominant language
R
Stars
3.9k
Forks
1.1k
Avg merge
14h 4m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Rdatatable/data.table

All issues in Rdatatable/data.table

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.