The memory manager now grows the heap more aggressively. This

reduces the number of garbage collections, in particular while

data or code are loaded, at the expense of slightly increasing the

one argument is an S4 object and S3 dispatch fails (due to

text rather than Windows progress bars in non-interactive use.

building and retrieving the help search database used by

, along with functions for inspecting the

concepts and keywords in the help search database.

Rd files which are not standard keywords (as given in

For standard keyword entries the corresponding descriptions are

for a numeric or logical matrix (which was always required).

, quite differently than proposed there.

coherently.  Unavoidably, this changes the display of such test

Code completion for namespaces now recognizes all loaded

namespaces, rather than only the ones that are also attached.

The code completion mechanism can now be replaced by a

user-specified completer function, for (temporary) situations

where the usual code completion is inappropriate.

will now warn if it is able to detect truncation

when unpacking a file of 4GB or more (related to

now force arguments to the functions they apply

in order to eliminate undesirable interactions between lazy

evaluation and variable capture in closures.  This resolves

It is possible to request the use of system

incompatibility of such headers discussed in the 'R Installation

now the default.  For the time being there is fallback to the

found or (unlikely) if they are too old.

package building, thanks to Dirk Eddelbuettel.

invisibly. The initial optimization level can also be set with the

specify an alternative set of tests to run.

testing after many types of errors, and will output a summary

count of errors at the end if any have occurred.

checks the existence and accessibility of URLs in the

files and in the help files (provided the build

reports non-ASCII characters in R source files when there

reports (apparent) S3 methods exported but not registered.

reports overwriting registered S3 methods from