forked from hadley/adv-r
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathTechniques.Rmd
9 lines (5 loc) · 1.19 KB
/
Techniques.Rmd
1
2
3
4
5
6
7
8
9
# (PART) Techniques {-}
# Introduction {.unnumbered}
The final four chapters cover two general programming techniques: finding and fixing bugs, and finding and fixing performance issues.
In Chapter \@ref(debugging), we'll first talking debugging, because finding the root cause of error can be extremely frustrating. Fortunately R has some great tools for debugging, and when they're coupled with a solid strategy, you should be able to find the root cause for most problems rapidly and relatively painlessly.
The remaining three chapters focus on performance, first measuring it (Chapter \@ref(perf-measure)) and then improving it (Chapters \@ref(perf-improve) and \@ref(rcpp)). Tools to measuring and improve performance are particularly important because R is not a fast language. This is not an accident: R was purposely designed to make interactive data analysis easier for humans, not to make computers as fast as possible. While R is slow compared to other programming languages, for most purposes, it's fast enough. These chapters help you handle the cases where is no longer fast enough, either by improving the performance of your R code, or by switching to a language, C++, that is designed for performance.