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

Improve performance for subsetting #790

Merged
merged 16 commits into from
Jun 23, 2020
Merged

Improve performance for subsetting #790

merged 16 commits into from
Jun 23, 2020

Conversation

krlmlr
Copy link
Member

@krlmlr krlmlr commented Jun 16, 2020

and prepare for continuous benchmarking.

@krlmlr krlmlr requested a review from hadley June 16, 2020 07:56
This was referenced Jun 23, 2020
@krlmlr krlmlr merged commit c07bb49 into master Jun 23, 2020
@krlmlr krlmlr deleted the f-subset-performance branch June 23, 2020 12:15
krlmlr added a commit that referenced this pull request Feb 25, 2021
tibble 3.0.2

- `[[` works with classed indexes again, e.g. created with `glue::glue()` (#778).
- `add_column()` works without warning for 0-column data frames (#786).
- `tribble()` now better handles named inputs (#775) and objects of non-vtrs classes like `lubridate::Period` (#784) and `formattable::formattable` (#785).

- Subsetting and subassignment are faster (#780, #790, #794).
- `is.null()` is preferred over `is_null()` for speed.
- Implement continuous benchmarking (#793).

- `is_vector_s3()` is no longer reexported from pillar (#789).
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants