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

slice always coerces output to a tibble #3297

Closed
hadley opened this issue Jan 9, 2018 · 1 comment
Closed

slice always coerces output to a tibble #3297

hadley opened this issue Jan 9, 2018 · 1 comment
Assignees
Labels

Comments

@hadley
Copy link
Member

@hadley hadley commented Jan 9, 2018

Even if it's a data frame

dplyr::slice(mtcars, 1)
#> # A tibble: 1 x 11
#>     mpg   cyl  disp    hp  drat    wt  qsec    vs    am  gear  carb
#>   <dbl> <dbl> <dbl> <dbl> <dbl> <dbl> <dbl> <dbl> <dbl> <dbl> <dbl>
#> 1  21.0  6.00   160   110  3.90  2.62  16.5     0  1.00  4.00  4.00

Created on 2018-01-09 by the reprex package
(0.1.1.9000)
.

@romainfrancois romainfrancois self-assigned this Mar 5, 2018
romainfrancois added a commit that referenced this issue Mar 5, 2018
@krlmlr krlmlr closed this in #3395 Mar 7, 2018
krlmlr added a commit that referenced this issue Mar 7, 2018
#3395)

* slice does not enforce tibble when input is a raw data.frame. closes #3297

* NEWS entry
krlmlr added a commit that referenced this issue Mar 13, 2018
* `slice()` no longer enforce tibble classes when input is a simple `data.frame`, and ignores 0 (#3297, #3313).
@lock
Copy link

@lock lock bot commented Sep 3, 2018

This old issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with reprex) and link to this issue. https://reprex.tidyverse.org/

@lock lock bot locked and limited conversation to collaborators Sep 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

3 participants