From f7a52c5fd456b97553b0037177764d63876fd9ef Mon Sep 17 00:00:00 2001 From: Mike-Hanna Date: Thu, 23 Oct 2025 13:25:23 -0400 Subject: [PATCH] copilot nitpicks --- instructions/r.instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/instructions/r.instructions.md b/instructions/r.instructions.md index 11081e8..2537832 100644 --- a/instructions/r.instructions.md +++ b/instructions/r.instructions.md @@ -48,7 +48,7 @@ Help GitHub Copilot generate idiomatic, safe, and maintainable R code across pro - **Data frames:** prefer tibbles in tidyverse-heavy files; otherwise base `data.frame()` is fine. - **Iteration:** use `purrr` in tidyverse code. In base-style code, prefer type-stable, vectorized patterns such as `vapply()` - (for atomic outputs) or `Map()` (for elementwise operations) instead of explicit `for` loops when they improve clarity or performance. + (for atomic outputs) or `Map()` (for elementwise operations) instead of explicit `for` loops when they improve clarity or performance. - **Strings & Dates:** use `stringr`/`lubridate` where already present; otherwise use clear base helpers (e.g., `nchar()`, `substr()`, `as.Date()` with explicit format). - **I/O:** prefer explicit, typed readers (e.g., `readr::read_csv()`); make parsing assumptions explicit.