RMI / RMI/resources

Piped calls to `return()`

Open
#93 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
No language data
Stars
17
Forks
5
PR merge metrics
No merged PRs in 30d

Description

R behaves strangely when you pipe a return() call.

https://stackoverflow.com/questions/59596950/strange-behaviour-when-piping-to-return-in-r-function

https://github.com/tidyverse/magrittr/issues/32

Easiest just to save the result of the pipe to an output, and return that.

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.

Research direction

Start by reviewing the linked Stack Overflow question and magrittr issue to confirm the reported R pipe and return() behavior. Then inspect this repository for the relevant resource or example; done means documenting or updating it with the suggested workaround of assigning the piped result before returning it.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.