Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend available Slicing Criterion Formats #1108

Open
EagleoutIce opened this issue Oct 25, 2024 · 2 comments · May be fixed by #1175
Open

Extend available Slicing Criterion Formats #1108

EagleoutIce opened this issue Oct 25, 2024 · 2 comments · May be fixed by #1175
Labels
documentation Improvements or additions to documentation static slicing Related to slicing the source code statically

Comments

@EagleoutIce
Copy link
Member

E.g. one to access the second use of x in a line to have something better then 1:6 in x <- x as 1@x matches the first one!

The documentation should be updated accordingly.

@EagleoutIce EagleoutIce added documentation Improvements or additions to documentation static slicing Related to slicing the source code statically labels Oct 25, 2024
@EagleoutIce
Copy link
Member Author

The discussion resolved with the decision to focus on a function-call/query like syntax (hoping that this can be merged/unified with #1087 later).

In short: a syntax like get(foo, 'last')/get(foo, -1) is preferred (additionally to the existing formats).

@EagleoutIce
Copy link
Member Author

We have agreed on a FlowR Search interface using a stream like processing approach.

@EagleoutIce EagleoutIce linked a pull request Nov 24, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation static slicing Related to slicing the source code statically
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant