Skip to content
New issue

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

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

Already on GitHub? # to your account

Implement continuous benchmarking #793

Closed
krlmlr opened this issue Jun 23, 2020 · 1 comment
Closed

Implement continuous benchmarking #793

krlmlr opened this issue Jun 23, 2020 · 1 comment
Milestone

Comments

@krlmlr
Copy link
Member

krlmlr commented Jun 23, 2020

Follow-up to #790.

@krlmlr krlmlr added this to the 3.1.0 milestone Jun 23, 2020
@krlmlr krlmlr closed this as completed in b2b1c39 Jul 5, 2020
krlmlr added a commit that referenced this issue Jul 5, 2020
- Implement continuous benchmarking (#793).

Closes #793.
krlmlr added a commit that referenced this issue 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
Copy link
Contributor

github-actions bot commented Jul 6, 2021

This old thread has been automatically locked. If you think you have found something related to this, please open a new issue and link to this old issue if necessary.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 6, 2021
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant