This blog is updated daily.
A general description is here.
‘grSoftVersion()’ now reports the versions of FreeType and FontConfig
if they are used directly (not _via_ Pango), as is most commonly done
on macOS.
(Not Windows.) ‘l10n_info()’ reports an additional element, the name of the encoding as reported by the OS.
‘grSoftVersion()’ now reports the versions of FreeType and FontConfig if they are used directly (not _via_ Pango), as is most commonly done on macOS.
macOS: Quartz device live drawing could fail (no plot is shown) if the system changes the drawing context after view update (often the case since macOS Big Sur). System log may show "CGContextDelegateCreateForContext: invalid context" error.
There is a further workaround for FreeType giving incorrect italic font faces with cairo-based graphics devices on macOS.
‘add_datalist(*, force = TRUE)’ (from package ‘tools’) now actually updates an existing ‘data/datalist’ file for new content, thanks to a report and patch by Sebastian Meyer in PR#18048.
‘cut.Date()’ and ‘cut.POSIXt()’ could produce an empty last interval for ‘breaks = "months"’ or ‘breaks = "years"’. Reported as PR#18053 by Christopher Carbone.
‘grSoftVersion()’ now reports the versions of FreeType and FontConfig if they are used directly (not _via_ Pango), as is most commonly done on macOS.
There is a new ‘configure’ option ‘--with-static-cairo’ which is the default on macOS. This should be used when only static cairo (and where relevant, Pango) libraries are available.
Cairo-based graphics devices on platforms without Pango but with freetype/fontconfig will make use of the latter for font selection.
Cairo installations without X11 are more likely to be detected by ‘configure’, when the file-based Cairo graphics devices will be available but not ‘X11(type = "cairo")’.
Too long lines in environment files (e.g. ‘Renviron’) no longer crash R. This limit has been increased to 100,000 bytes (PR#18001).
File ‘share/texmf/tex/latex/jss.cls’ has been updated to work with LaTeX versions since Oct 2020.
Unicode character width tables (as used by ‘nchar(, type = "w")’) have been updated to Unicode 12.1 by Brodie Gaslam (PR#17781), including many emoji.
The internal table for ‘iswprint’ (used on Windows, macOS and AIX) has been updated to include many recent Unicode characters.
If an external BLAS is specified by ‘--with-blas=foo’ or _via_ environment variable ‘BLAS_LIBS’ is not found, this is now a configuration error. The previous behaviour was not clear from the documentation: it was to continue the search as if ‘--with-blas=yes’ was specified.
‘all.equal(x,y)’ now “sees” the two different ‘NA’s in factors, thanks to Bill Dunlap and others in PR#17897.
‘(~ NULL)[1]’ and similar formula subsetting now works, thanks to a report and patch by Henrik Bengtsson in PR#17935. Additionally, subsetting leaving an empty formula now works too, thanks to suggestions by Suharto Anggono.
‘.traceback(n)’ keeps source references again, as before R 4.0.0, fixing a regression; introduced by the PR#17580, reported including two patch proposals by Brodie Gaslam.
‘unlist(plst, recursive=FALSE)’ no longer drops content for pairlists with list components, thanks to the report and patch by Suharto Anggono in PR#17950.
‘iconvlist()’ now also works on MUSL based (Linux) systems, from a report and patch suggestion by Wesley Chan in PR#17970.
‘round()’ and ‘signif()’ no longer tolerate wrong argument names, notably in 1-argument calls; reported by Shane Mueller on R-devel (mailing list); later reported as PR#17976.
‘.Machine’ has ‘longdouble.*’ elements only if ‘capabilities("long.double")’ is true, as documented. (Previously they were included if the platform had ‘long double’ identical to ‘double’, as ARM does.)
‘p.adjust(numeric(), n=0)’ now works, fixing PR#18002.
‘identical(x,y)’ no longer prints "Unknown Type .." for ‘typeof(x) == "..."’ objects.
Fix (auto-)‘print()’ing of named complex vectors, see PR#17868 and PR#18019.
‘all.equal(<language>, <...>)’ now works, fixing PR#18029.
‘as.data.frame.list(L, row.names=NULL)’ now behaves in line with ‘data.frame()’, disregarding names of components of ‘L’, fixing PR#18034, reported by Kevin Tappe.
‘checkRdaFiles(ff)$version’ is now correct also when ‘ff’ contains files of different versions, thanks to a report and patch from Sebastian Meyer in PR#18041.
Message translation domains, e.g., for errors and warnings, are now correctly determined also when e.g., a ‘base’ function is called from “top-level” function (i.e., defined in ‘globalenv()’), thanks to a patch from Joris Goosen fixing PR#17998.
There is optional support for tracing the progress of ‘loadNamespace’ - see its help.
Subsetting/indexing, such as ‘ddd[*]’ or ‘ddd$x’ on a ‘DOTSXP’ (dot-dot-dot) object ‘ddd’ has been disabled; it worked by accident only, undocumentedly.
‘as.data.frame.list(L, row.names=NULL)’ now behaves in line with
‘data.frame()’, disregarding names of components of ‘L’, fixing
PR#18034, reported by Kevin Tappe.
‘as.data.frame.list(L, row.names=NULL)’ now behaves in line with ‘data.frame()’, disregarding names of components of ‘L’, fixing PR#18034, reported by Kevin Tappe.
‘checkRdaFiles(ff)$version’ is now correct also when ‘ff’ contains files of different versions, thanks to a report and patch from Sebastian Meyer in PR#18041.
The default C++ standard has been changed to C++14 where available (which it is on all currently checked platforms): if not (as before) C++11 is used if available otherwise C++ is not supported.
Packages which specify C++11 will still be installed using C++11.
C++14 compilers may give deprecation warnings, most often for ‘std::random_shuffle’ (deprecated in C++14 and removed in C++17). Either specify C++11 (see ‘Writing R Extensions’) or modernize the code and if needed specify C++14. The latter has been supported since R 3.4.0 so the package's ‘DESCRIPTION’ would need to include something like
Depends: R (>= 3.4)
The default C++ standard has been changed to C++14 where available (which it is on all currently checked platforms): if not (as before) C++11 is used if available otherwise C++ is not supported.
Packages which specify C++11 will still be installed using C++11.
C++14 compilers may give deprecation warnings, most often for ‘std::random_shuffle’ (deprecated in C++14 and removed in C++17). Either specify C++11 (see ‘Writing R Extenions’) or modernize the code and if needed specify C++14. The latter has been supported since R 3.4.0 so the package's ‘DESCRIPTION’ would need to include something like
Depends: R (>= 3.4)
The default personal library directory on builds with ‘--enable-aqua’ (including CRAN builds) now differs by CPU type, one of
~/Library/R/x86_64/x.y/library ~/Library/R/arm64/x.y/library
Subsetting/indexing, i.e. ‘ddd[*]’ on a ‘DOTSXP’ (dot-dot-dot) object ‘ddd’ has been disabled; it worked by accident only, undocumentedly.
‘str()’ now works correctly for DOTSXP and related exotics, even when these are doomed.
Additionally, it no longer fails for ‘list’s with a ‘class’ and “irregular” method definitions such that e.g. ‘lapply(*)’ will necessarily fail, as currently for different ‘igraph’ objects.
‘as.data.frame.list(L, row.names=NULL)’ now behaves in line with ‘data.frame()’, disregarding names of components of ‘L’, fixing PR#18034, reported by Kevin Tappe.
‘capabilities("cairo")’ now applies only to the file-based devices as it is now possible (if very unusual) to build R with Cairo support for those but not for ‘X11()’.
‘all.equal()’ no longer gives an error on ‘DOTSXP’ objects.
The ‘grid’ package now allows ‘gpar(fill)’ to be a ‘linearGradient()’, a ‘radialGradient()’, or a ‘pattern()’. The ‘viewport(clip)’ can now also be a grob, which defines a clipping path, and there is a new ‘viewport(mask)’ that can also be a grob, which defines a mask.
These new features are only supported (so far) on Cairo-based graphics devices and the ‘pdf()’ device.
Cairo installations without X11 are more likely to be detected by ‘configure’, when the file-based Cairo devices will be available but not ‘X11(type = "cairo")’.
Pango installations using static libraries on macOS are more likely to be detected.
The default personal library directory on builds with ‘--enable-aqua’ (includingCRAN builds) now differs by CPU type, one of
~/Library/R/x86_64/x.y/library ~/Library/R/arm64/x.y/library
‘str()’ now works correctly for DOTSXP and related exotics, even when these are doomed.
The default personal library directory on CRAN builds now differs by CPU type, one of
~/Library/R/x86_64/x.y/library ~/Library/R/arm64/x.y/library
‘names()’ now works for ‘DOTSXP’ objects. On the other hand, in ‘R-lang’, the R language manual, we now warn against relying on the structure or even existence of such ‘dot-dot-dot’ objects.
‘all.equal()’ no longer errors on ‘DOTSXP’ objects.
R now provides a shorthand notation for creating functions, e.g. ‘\(x) x + 1’ is parsed as ‘function(x) x + 1’. This feature is experimental and may change prior to release.
R now provides a simple native forward pipe syntax ‘|>’. The simple form of the forward pipe inserts the left-hand side as the first argument in the right-hand side call. A syntax is also provided for passing the left-hand side as an argument other than the first. The pipe implementation as a syntax transformation was motivated by suggestions from Jim Hester and Lionel Henry. This feature is experimental and may change prior to release.
R now provides a simple native froward pipe syntax ‘|>’. The simple form of the forward pipe inserts the left-hand side as the first argument in the right-hand side call. A syntax is also provided for passing the left-hand side as an argument other than the first. The pipe implementation as a syntax transformation was motivated by suggestions from Jim Hester and Lionel Henry. This feature is experimental and may change prior to release.
R now provides a shorthand notation for creating functions, e.g. ‘\(x) x + 1’ is parsed as ‘function(x) x + 1’. This features is experimental and may change prior to release.
‘identical(x,y)’ is no longer true for differing ‘DOTSXP’ objects, fixing PR#18032.
‘all.equal(<language>, <...>)’ now works, fixing PR#18029.
The character-classification functions used (by default) to replace the system ‘iswxxxxx’ functions on Windows, macOS and AIX have been updated to Unicode 13.0.0.
The character-width tables have been updated to include new assignments in Unicode 13.0.0.
The internal table for ‘iswprint’ (used on Windows, macOS and AIX) has been updated to include many recent Unicode characters.
The character-classification functions used (by default) to replace the system ‘iswxxxxx’ functions on Windows, macOS and AIX have been updated to Unicode 13.0.0 - in particular, many more UTF-8 characters (such as emojis) are regarded as printable.
The character-width tables have been updated to include new assignments in Unicode 13.0.0.
The code for evaluating default (extended) regular expressions now uses the same character-classification functions as the rest of R (previously they differed on Windows, macOS and AIX.)
There is a build-time option to replace the system's wide-character ‘wctrans’ C function by tables shipped with R: use ‘configure’ option ‘--with-internal-towlower’ or (on Windows) ‘-DUSE_RI18N_CASE’ in ‘CFLAGS’ when building R. This may be needed to allow ‘tolower()’ and ‘toupper()’ to work with Unicode characters beyond the Basic Multilingual Plane where not supported by system functions (e.g. on Solaris where it is the new default).
Lithuanian translations are now available, thanks to Rimantas Žakauskas.
Cairo installations without X11 are more likely to be detected by ‘configure’.
There are new ‘configure’ options ‘--with-internal-iswxxxxx’, ‘--with-internal-towlower’ and ‘--with-internal-wcwidth’ which allows the system functions for wide-character classification, case-switching and width (‘wcwidth’ and ‘wcswidth’) to be replaced by internal ones. The first has long been used on macOS, AIX (and Windows) but this enables it to be unselected there and selected for other platforms (it is the new default on Solaris). The second is new in this version of R and is selected by default on macOS and Solaris. The third has long been the default and remains so as it contains customizations for East Asian languages.
System versions of these functions are often minimally implemented (sometimes only for ASCII characters) and may not cover the full range of Unicode points: for example Solaris (and Windows) only cover the Basic Multilingual Plane.
There are new ‘configure’ options ‘--with-internal-iswxxxxx’, ‘--with-internal-towlower’ and ‘--with-internal-wcwidth’ which allows the system functions for wide-character classification, case-switching and width (‘wcwidth’ and ‘wcswidth’) to be replaced by internal ones. The first has long been used on macOS, AIX (and Windows) but this enables it to be unselected there and selected for other platforms (it is the new default on Solaris). The second is new in this version of R and is selected by default on macOS and Solaris. The third has long been the default and remains so as it contains customizations for East Asian languages.
System versions of these functions are often minimally implemented (sometimes only for ASCII characters) and do not cover the full range of Unicode points: for example Solaris (and Windows) only cover the Basic Multilingual Plane.
Unicode character width tables (as used by ‘nchar(, type="w")’) have
been updated to Unicode 12.1 by Brodie Gaslam (PR#17781).
The parser now treats ‘\Unnnnnnnn’ escapes larger than the upper limit for Unicode points (‘\U10FFFF’) as an error as they cannot be represented by valid UTF-8.
Where such escapes are used for outputting non-printable (including unassigned) characters, 6 hex digits are used (rather than 8 with leading zeros). For clarity, braces are used, for example ‘\U{0effff}’.
There is a build-time option to replace the system's wide-character ‘wctrans’ C function by tables shipped with R: use ‘configure’ option ‘--with-internal-towlower’ or (on Windows) ‘-DUSE_RI18N_CASE’ in ‘CFLAGS’ when building R. This may be needed to allow ‘tolower()’ and ‘toupper()’ to work with Unicode characters beyond the Basic Multilingual Plan where on supported by system functions (e.g. on Solaris where it is the new default).
Unicode character width tables (as used by ‘nchar(, type = "w")’) have been updated to Unicode 12.1 by Brodie Gaslam (PR#17781), including many emoji.
Unicode character width tables (as used by ‘nchar(, type="w")’) have
been updated to Unicode 12.1 by Brodie Gaslam (PR#17781).
There are new ‘configure’ options ‘--with-internal-iswxxxxx’ and ‘--with-internal-towlower’ which allows the system wide-character classification and case-switching routines to be replaced by internal ones. The first has long been used on macOS, AIX (and Windows) but this enables it to be unselected there and selected for other platforms (it is the new default on Solaris). The second is new in this version of R and is selected by default on macOS and Solaris.
System versions of these functions are often minimally implemented (sometimes only for ASCII characters) and do not cover the full range of Unicode points: for example Solaris (and Windows) only cover the Basic Multilingual Plane.
Unicode character width tables (as used by ‘nchar(, type="w")’) have been updated to Unicode 12.1 by Brodie Gaslam (PR#17781).
The character-classification functions used (by default) to replace the system ‘iswxxxxx’ functions on Windows, macOS and AIX have been updated to Unicode 13.0.0 - in particular, many more UTF-8 characters (such as emojis) are regarded as printable.
There is a build-time option to replace the system's wide-character ‘wctrans’ C function by tables shipped with R: use ‘configure’ option ‘--with-internal-towlower’ or (on Windows) ‘-DUSE_RI18N_CASE’ in ‘CFLAGS’ when building R. This allows ‘tolower()’ and ‘toupper()’ to work with Unicode characters beyond the Basic Multilingual Plan where on supported by system functions (e.g. on Solaris where it is the new default).
There are new ‘configure’ options ‘--with-internal-iswxxxx’ and ‘--with-internal-towlower’ which allows the system wide-character classification and case-switching routines to be replaced by internal ones. The first has long been used on macOS, AIX (and Windows) but this enables it to be unselected there and selected for other platforms. The second is new in this version of R and is selected by default on macOS.
System versions of these functions are often minimally implemented (sometimes only for ASCII characters) and do not cover the full range of Unicode points: for example Solaris (and Windows) only cover the Basic Multilingual Plane.
The character-classification functions used (by default) to replace the system ‘iswxxxx’ functions on Windows, macOS and AIX have been updated to Unicode 13.0.0 - in particular, many more UTF-8 characters are regarded as printable.
There is a build-time option to replace the system's wide-character ‘wctrans’ C function by tables shipped with R: use ‘configure’ option ‘--with-internal-towlower’ or (on Windows) ‘-DUSE_RI18N_CASE’ in ‘CFLAGS’ when building R. On Windows and Solaris this allows ‘tolower()’ and ‘toupper()’ to work with Unicode characters beyond the Basic Multilingual Plane and is intended to become the default there.
The parser now treats ‘\Unnnnnnnn’ escapes larger than the upper limit for Unicode points (‘\U10FFFF’) as an error as they cannot be represented by valid UTF-8.
Where such escapes are used for outputting non-printable (inclduing unassigned) characters, 6 hex digits are used (rather than 8 with leading zeros). For clarity, braces are used, for example ‘\U{0effff}’.
There are warnings (including from the parser) on the use of unpaired surrogate Unicode points such as ‘\uD834’. (These cannot be converted to valid UTF-8).
The code for evaluating default (extended) regular expressions now uses the same character-classification functions as the rest of R (they previously differed on Windows, macOS and AIX.)
C99 function ‘iswblank’ is required - it was last seen missing ca 2003 so the workaround has been removed.
The parser now looks for non-ASCII spaces on Solaris, in addition to
Windows, macOS, FreeBSD and OSes such as Linux that declare ‘wchar_t’
is encoded as Unicode.
The parser now looks for non-ASCII spaces on Solaris (as previously on most other OSes).
Functions ‘nchar()’, ‘tolower()’, ‘toupper()’ and ‘chartr()’ and those using regular expressions have more support for inputs with a marked Latin-1 encoding.
Parsing strings containing UTF-16 surrogate pairs such as ‘"\uD834\uDD1E"’ works better on some (uncommon) platforms. ‘sprintf("%X", utf8ToInt("\uD834\uDD1E"))’ should now give ‘"1D11E"’ on all platforms.
‘nchar()’, ‘tolower()’, ‘toupper()’ and ‘chartr()’ have more support for inputs with a marked encoding (UTF-8 or Latin-1) in a single-byte locale.
The parser now treats ‘\Unnnnnnnn’ escapes larger than the upper limit for Unicode points (‘\U10FFFF’) as an error as they cannot be represented by valid UTF-8.
Where such escapes are used for outputting non-printable characters, 6 (not 8) hex digits are used (as it was decided by Unicode that the first two would always be zero).
The parser now looks for non-ASCII spaces on Solaris, in addition to Windows, macOS, FreeBSD and OSes such as Linux that declare ‘wchar_t’ is encoded as Unicode.
There are warnings (including from the parser) on the use of unpaired surrogate Unicode points such as ‘\uD834’ (which cannot be converted to valid UTF-8).
‘tolower()’, ‘toupper()’ and ‘chartr()’ have more support for inputs with a marked encoding (UTF-8 or Latin-1) in a single-byte locale.
The code for the evaluating default (extended) regular expressions now uses the same character-classification functions as the rest of R; in some cases (Windows, AIX, macOS) these replace limited system ones, the differences being in non-Latin characters.
The parser now treats ‘\Unnnnnnnn’ escapes larger than the upper limit
for Unicode points (‘\U10FFFF’) as an error as they cannot be
represented by valid UTF-8.
Where such escapes are used for outputting non-printable characters, 6 (not 8) hex digits are used (as it was decided by Unicode that the first two would always be zero).
Code converting UTF-8 strings (e.g., ‘tolower()’ and some ‘printing’)
now uses internal routines rather than system functions: these detect
more uses of invalid UTF-8 strings.
There are warnings (including from the parser) on the use of unpaired surrogate Unicode points such as ‘\uD834’ (which cannot be converted to valid UTF-8).
‘.libPaths()’ gets a new option ‘include.site’, allowing to _not_ include the site library, thanks to Dario Strbenac's suggestion and Gabe Becker's PR#18016.
Code converting UTF-8 strings (e.g., ‘tolower()’ and some ‘printing’) now uses internal routines rather than system functions: these detect more uses of invalid UTF-8 strings.
There are warnings (including from the parser) on the use of unpaired surrogate Unicode points such as ‘\uD834’ (which cannot be converted to valid UTF-8).
The parser now treats ‘\Unnnnnnnn’ escapes larger than the upper limit for Unicode points (‘\U10FFFF’) as an error as they cannot be represented by valid UTF-8.
Where such escapes are used for outputting non-printable characters, 6 (not 8) hex digits are used (as it was decided by Unicode that the first two would always be zero).
Code converting UTF-8 strings (e.g., ‘tolower()’ and some ‘printing’) now uses internal routines rather than system functions: these detect more uses of invalid UTF-8 strings.
‘identical(x,y)’ no longer prints "Unknown Type .." for ‘typeof(x) == "..."’ objects.
Code converting UTF-8 strings (e.g., ‘tolower()’ and some ‘printing’ now uses internal routines rather than system functions: these detect more uses of invalid UTF-8 strings.
The parser now treats ‘\Unnnnnnnn’ escapes larger than the upper limit for Unicode points (‘\U10FFFF’) as an error as they cannot be represented by valid UTF-8.
Where such escapes are use for outputting non-printable characters, 6 (not 8) hex digits are used (as it was decided by Unicode that the first two would always be zero).
The parser now treats ‘\Unnnnnnnn’ escapes larger than ‘"\U10FFFF"’ as an error as they cannot be represented by valid UTF-8.
Where such escapes are use for outputting non-printable characters, 6 (not 8) hex digits are used (as it was decided that the first two would always be zero).
‘all.equal(f, g)’ for ‘function’s now by default also compares their ‘environment(.)’s, notably via new ‘all.equal’ method for class ‘function’. Comparison of ‘nls()’ fits, e.g., may now need ‘all.equal(m1, m2, check.environment = FALSE)’.
Parsing strings containing UTF-16 surrogate pairs such as ‘"\uD834\uDD1E"’ works better on some (uncommon) platforms.
‘unsplit()’ had trouble with tibbles due to unsound use of ‘rep(NA, len)’-indexing, which should use ‘NA_integer_’ Reported to R-devel by Mario Annau.
‘pnorm(x, log.p = TRUE)’ underflows to ‘-Inf’ slightly later.
‘show(<hidden S4 generic>)’ prints better and without quotes for non-hidden S4 generics.
‘read.table()’ and relatives treated an "NA" column name as missing when ‘check.names = FALSE’ PR#18007.
File ‘share/texmf/tex/latex/jss.cls’ has been updated to work with LaTeX versions since Oct 2020.
(Not Windows.) A warning is given when a Cairo-based type is specified for a ‘png()’, ‘jpeg()’, ‘tiff()’ or ‘bmp()’ device but Cairo is unsupported (so ‘type = "Xlib"’ is tried instead).
‘read.table()’ and relatives treated an "NA" column name as missing when ‘check.names=FALSE’ PR#18007.
‘all.equal(f, g)’ for ‘function’s now by default also compares their ‘environment(.)’s, notably via new ‘all.equal’ method for class ‘function’. Comparison of ‘nls()’ fits, e.g., may now need ‘all.equal(m1, m2, check.environment=FALSE)’.
‘p.adjust(numeric(), n=0)’ now works, fixing PR#18002.
‘all.equal(f, g)’ for ‘function’s now by default also compares their ‘environment(.)’s, notably via new ‘all.equal’ method for class ‘function’. Comparison of ‘nls()’ fits, e.g., may now need ‘all.equal(m1, m2, check.environments=FALSE)’.
R now provides a simple native pipe syntax ‘|>’ as well as a shorthand notation for creating functions, e.g. ‘\(x) x + 1’ is parsed as ‘function(x) x + 1’. The pipe implementation as a syntax transformation was motivated by suggestions from Jim Hester and Lionel Henry. These features are experimental and may change prior to release.
‘R CMD check’ etc now warn when a package exports non-existing S4 classes or methods, also in case of no "methods" presence; reported by Alex Bertram; reproducible example and patch by Sebastian Meyer in PR#16662.
If an external BLAS is specified by ‘--with-blas=foo’ or _via_ environment variable ‘BLAS_LIBS’ is not found, this is now a configuration error. The previous behaviour was not clear from the documentation: it was to continue the search as if ‘--with-blas=yes’ was specified.
‘show(<hidden S4 generic>)’ prints better.
Functions ‘URLencode()’ and ‘URLdecode()’ in package ‘utils’ now work on vectors of URIs. Based on patch from Bob Rudis submitted with PR#17873.
Function ‘...elt()’ now propagates visibility consistently with ‘..n’, thanks to Lionel Henry's PR#17905.
‘packBits(bits, type="double")’ now works as inverse of ‘numToBits()’, thanks to Bill Dunlap's proposal in PR#17914.
‘curlGetHeaders()’ has two new arguments, ‘timeout’ to specify the timeout for that call (overriding ‘getOption("timeout")’) and ‘TLS’ to specify the minimum TLS protocol version to be used for ‘https://’ URIs (_inter alia_ providing a means to check for sites using deprecated TLS versions 1.0 and 1.1).
Numeric differentiation _via_ ‘numericDeriv()’ gets new optional arguments ‘eps’ and ‘central’, the latter for taking central divided differences. The latter can be activated for ‘nls()’ via ‘nls.control(nDcentral = TRUE)’.
‘nls()’ now passes the ‘trace’ and ‘control’ arguments to ‘getInitial()’, notably for all self-starting models, so these can also be fit in zero-noise situations via a ‘scaleOffset’. For this reason, the ‘initial’ function of a ‘selfStart’ model must now have ‘...’ in its argument list.
‘get()’, ‘exists()’, and ‘get0()’ now signal an error if the first argument has length greater than 1. Previously additional elements were silently ignored. Suggested by Antoine Fabri on R-devel.
The graphics engine version, ‘R_GE_version’, has been bumped to ‘14’ and so packages that provide graphics devices should be reinstalled.
‘R CMD INSTALL’ and ‘R CMD SHLIB’ make use of their flag ‘--use-LTO’ when the ‘LTO_OPT’ make macro is set in file ‘etc/${R_ARCH}/Makeconf’ or in a personal/site ‘Makevars’ file. (For details see ‘Writing R Extensions’ §4.5.)
This provides a valuable check on code consistency. It does work with GCC 8.3 as in Rtools40, but that does not detect everything the CRAN checks with current GCC do.
‘R CMD check’ etc now warn when a package exports non-existing S4 classes or methods, also in case of no "methods" presence; reported by Alex Bertram; reprpducible example and patch by Sebastian Meyer in PR#16662.
‘.Machine’ has ‘longdouble.*’ elements only if ‘capabilities("long.double")’ is true, as documented. (Previously they were included if the platform had ‘long double’ identical to ‘double’, as ARM does.)
If an external BLAS is specified by ‘--with-blas=foo’ or _via_ envionmental variable ‘BLAS_LIBS’ is not found, this is now a configuration error. The previous behaviour was not clear from the documentation: it was to continue the search as if ‘--with-blas=yes’ was specified.
‘.Machine’ has ‘longdouble.*’ elements only if ‘capabilities("long.double")’ is true, as documented. (Previously they were included if the platform had ‘long double’ idential to ‘double’, as ARM does.)
Data set ‘esoph’ in package ‘datasets’ now provides the correct numbers of controls; previously it had the numbers of cases added to these. Reported by Alexander Fowler in PR#17964.
‘pnorm(x, log.p=TRUE)’ underflows to ‘-Inf’ slightly later.
‘get()’, ‘exists()’, and ‘get0()’ now signal an error if the first argument has length greater than 1. Preciously additional elements were silently ignored. Suggested by Antoine Fabri on R-devel.
‘unsplit()’ had trouble with tibbles due to unsound use of ‘rep(NA,len)’-indexing, which should use ‘NA_integer_’ Reported to R-devel by Mario Annau.
‘round()’ and ‘signif()’ no longer tolerate wrong argument names,
notably in 1-argument calls; reported by Shane Mueller on the R-devel
mailing list.
‘round()’ and ‘signif()’ no longer tolerate wrong argument names, notably in 1-argument calls; reported by Shane Mueller on R-devel (mailing list); later reported as PR#17976.
‘iconvlist()’ now also works on MUSL based (Linux) systems, from a report and patch suggestion by Wesley Chan in PR#17970.
‘textConnection()’ gets an optional ‘name’ argument.
Graphics devices should now specify ‘deviceVersion’ to indicate what version of the graphics engine they support.
The graphics engine version, ‘R_GE_version’, has been bumped to 14 and so packages that provide graphics devices should be reinstalled.
Graphics devices can now specify ‘deviceClip’. If ‘TRUE’, the graphics engine will never perform any clipping of output itself.
The clipping that the graphics engine does perform (for both ‘canClip = TRUE’ and ‘canClip = FALSE’) has been improved to avoid producing unnecessary artifacts in clipped output.
‘nls()’ now passes the ‘trace’ and ‘control’ arguments to ‘getInitial()’, notably for all self-starting models, so these can also be fit in zero-noise situations via a ‘scaleOffset’. For this reason, the ‘initial’ function of a ‘selfStart’ model now must have ‘...’ in its argument list.
‘bquote(splice = TRUE)’ can now splice expression vectors with attributes: this makes it possible to splice the result of ‘parse(keep.source = TRUE)’. Report and patch provided by Lionel Henry in PR#17869.
‘nls()’ now passes the ‘trace’ and ‘control’ arguments to ‘getInitial()’, notably for all selfStart models, so these can also be fit in zero-noise situations via a ‘scaleOffset’.
‘bquote()’ can now splice expression vectors with attributes. This makes it possible to splice the result of ‘parse(keep.source = TRUE)’. Report and patch provided by Lionel Henry in PR#17869.
Numeric differentiation ‘numericDeriv()’ gets new optional arguments ‘eps’ and ‘central’, the latter for taking central divided differences. That can be activated for ‘nls()’ via ‘nls.control(nDcentral = TRUE)’.
For ‘nls()’, an optional constant ‘scaleOffset’ may be added to the denominator of the relative offset convergence test for cases where the fit of a model is expected to be exact, thanks to a proposal by John Nash. ‘nls(*, trace=TRUE)’ now also shows the convergence criterion.
‘.traceback(n)’ keeps source references again, as before R 4.0.0,
fixing a regression; introduced by the PR#17580, reported including two
patch proposals by Brodie Gaslam.
‘.traceback(n)’ keeps source references again, as before R 4.0.0, fixing a regression; introduced by the PR#17580, reported including two patch proposals by Brodie Gaslam.
‘unlist(plst, recursive=FALSE)’ no longer drops content for pairlists with list components, thanks to the report and patch by Suharto Anggono in PR#17950.
For ‘nls()’, an optional constant ‘scaleOffset’ may be added to the denominator of the relative offset convergence test for cases where the fit of a model is expected to be exact, thanks to a proposal by John Nash.
‘sum(df)’ and similar ‘"Summary"’- and ‘"Math"’-group member functions now work for data frames ‘df’ with ‘logical’ columns, notably also of zero rows. Reported to R-devel by Martin "b706".
‘qnorm(<very large negative>, log.p=TRUE)’ is now correct to at least five digits where it was catastrophically wrong, previously.
‘all.equal(x,y)’ now “sees” the two different ‘NA’s in factors, thanks to Bill Dunlap and others in PR#17897.
‘(~ NULL)[1]’ and similar formula subsetting now works, thanks to a report and patch by Henrik Bengtsson in PR#17935. Additionally, subsetting leaving an empty formula now works too, thanks to suggestions by Suharto Anggono.
‘all.equal(x,y)’ now “sees” the two different ‘NA’s in factors, thanks
to Bill Dunlap and others in PR#17897.
‘(~ NULL)[1]’ and similar formula subsetting now works, thanks to a
report and patch by Henrik Bengtsson in PR#17935. Additionally,
subsetting leaving an empty formula now works too, thanks to
suggestions by Suharto Anggono.
‘curlGetHeaders()’ has two new arguments, ‘timeout’ to specify the timeout for that call (overriding ‘getOption("timeout")’) and ‘TLS’ to specify the minimum TLS protocol version to be used for ‘https://’ URLs (_inter alia_ providing a means to check for sites using deprecated TLS versions 1.0 and 1.1).
‘capture.output()’ no longer uses non-standard evaluation to evaluate its arguments. This makes evaluation of functions like ‘parent.frame()’ more consistent, thanks to Lionel Henry's PR#17907.
‘.traceback(n)’ keeps source references again, as before R 4.0.0, fixing a regression; introduced by the PR#17580, reported including two patch proposals by Brodie Gaslam.
‘x[[2^31]] <- v’ now works, thanks to the report and patch by Suharto Anggono in PR#17330.
In log-scale graphics, ‘axis()’ ticks and label positions are now computed more carefully and symmetrically in their range, typically providing _more_ ticks, fulfilling wishes in PR#17936. The change really corresponds to an improved ‘axisTicks()’ (package ‘grDevices’), potentially influencing ‘grid’ and ‘lattice’, for example.
‘(~ NULL)[1]’ and similar formula subsetting now works, thanks to a report and patch by Henrik Bengtsson in PR#17935. Additionally, subsetting leaving an empty formula now works too, thanks to suggestions by Suharto Anggono.
‘(~ NULL)[1]’ and similar formula subsetting now works, thanks to a report and patch by Henrik Bengtsson in PR#17935.
‘as.POSIXct()’ now populates the ‘"tzone"’ attribute from its ‘tz’ argument when ‘x’ is a logical vector consisting entirely of ‘NA’ values.
The default value for ‘options("timeout")’ can be set from environment variable ‘R_DEFAULT_INTERNET_TIMEOUT’, still defaulting to 60 (seconds) if that is not set or invalid.
This may be needed when child R processes are doing downloads, for example during the installation of source packages which download jars or other forms of data.
On platforms using ‘configure’ option ‘--with-internal-tzcode’, additional values ‘"internal"’ and (on macOS only) ‘"macOS"’ are accepted for the environment variable ‘TZDIR’. (See ‘?TZDIR’.)
On macOS, ‘"macOS"’ is used by default if the system timezone database is a newer version than that in the R installation.
When ‘install.packages(type = "source")’ fails to find a package in a repository it mentions package versions which are excluded by their R version requirement and links to hints on why a package might not be found.
The default value for ‘options("timeout")’ can be set from enviromnent variable ‘R_DEFAULT_INTERNET_TIMEOUT’, still defaulting to 60 (seconds) if that is not set or invalid.
This may be needed when child R processes are doing downloads, for example during the installation of source packages which download jars or other forms of data.
There is now support for parallelized Link-Time Optimization (LTO) with GCC and for ‘thin’ LTO with ‘clang’ _via_ setting the ‘LTO’ macro.
There is support for setting a different LTO flag for the Fortran compiler, including to empty when mixing ‘clang’ and ‘gfortran’ (as on macOS). See file ‘config.site’.
There is a new ‘LTO_LD’ macro to set linker options for LTO compilation, for example to select an alternative linker or to parallelize thin LTO.
The ‘LINPACK’ argument to ‘chol.default()’, ‘chol2inv()’, ‘solve.default()’ and ‘svd()’ has been defunct since R 3.1.0. Using it now gives a warning which will become an error in R 4.1.0.
The code mitigating stack overflow with PCRE regexps on very long strings is enabled for PCRE2 < 10.30 also when JIT is enabled, since stack overflows have been seen in that case.
Fix to correctly show the group labels in ‘dotchart()’ (which where lost in the ‘ylab’ improvement for R 4.0.0).
‘addmargins(*, ..)’ now also works when ‘fn()’ is a local function, thanks to bug report and patch PR#17124 from Alex Bertram.
‘rank(x)’ and hence ‘sort(x)’ now work when ‘x’ is an object (as per ‘is.object(x)’) of type ‘"raw"’ _and_ provides a valid ‘`[`’ method, e.g., for ‘gmp::as.bigz(.)’ numbers.
‘chisq.test(*, simulate.p.value=TRUE)’ and ‘r2dtable()’ now work correctly for large table entries (in the millions). Reported by Sebastian Meyer and investigated by more helpers in PR#16184.
Low-level socket read/write operations have been fixed to correctly signal communication errors. Previously, such errors could lead to a segfault due to invalid memory access. Reported and debugged by Dmitriy Selivanov in PR#17850.
‘quantile(x, pr)’ works more consistently for ‘pr’ values slightly outside [0,1], thanks to Suharto Anggono's PR#17891.
Further, ‘quantile(x, prN, names=FALSE)’ now works even when ‘prN’ contains ‘NA’s, thanks to Anggono's PR#17892. Ditto for ordered factors or ‘Date’ objects when ‘type = 1’ or ‘3’, thanks to PR#17899.
Libcurl-based internet access, including ‘curlGetHeaders()’, was not respecting the ‘"timeout"’ option. If this causes unanticipated timeouts, consider increasing the default by setting ‘R_DEFAULT_INTERNET_TIMEOUT’.
‘as.Date(<char>)’ now also works with an initial ‘""’, thanks to Michael Chirico's PR#17909.
‘isS3stdGeneric(f)’ now detects an S3 generic also when it it is ‘trace()’d, thanks to Gabe Becker's PR#17917.
‘R_allocLD()’ has been fixed to return memory aligned for long double type PR#16534.
‘fisher.test()’ no longer segfaults when called again after its internal stack has been exceeded PR#17904.
Accessing a long vector represented by a compact integer sequence no longer segfaults (reported and debugged by Hugh Parsonage).
‘duplicated()’ now works also for strings with multiple encodings inside a single vector PR#17809.
‘tar()’ no longer skips non-directory files, thanks to a patch by Sebastian Meyer, fixing the remaining part of PR#16716.
‘phyper(11, 15, 0, 12, log.p=TRUE)’ no longer gives ‘NaN’; reported as PR#17271 by Alexey Stukalov.
Fix incorrect calculation in ‘logLik.nls()’ PR#16100, patch from Sebastian Meyer.
A very old bug could cause a segfault in ‘model.matrix()’ when terms involved logical variables. Part of PR#17879.
‘model.frame.default()’ allowed ‘data = 1’, leading to involuntary variable capture (rest of PR#17879).
Libcurl-based internet access, including ‘curlGetHeaders()’, was not respecting the ‘"timeout"’ option. If this causes unanticipated timeouts, consider increasing the default by setting ‘R_DEFAULT_INTERNET_TIMEOUT’.
The default value for ‘options("timeout")’ can be set from enviromnent variable ‘R_DEFAULT_INTERNET_TIMEOUT’, still defaulting to 60 (seconds) if that is not set or invalid.
This may be needed when child R processes are doing downloads, for example during the installation of source packages which download jars or other forms of data.
‘phyper(11, 15, 0, 12, log.p=TRUE)’ no longer gives ‘NaN’; reported as
PR#17271 by Alexey Stukalov.
A very old bug could cause a segfault in ‘model.matrix()’ when terms
involved logical variables. Related to PR#17879, but not a complete
fix for that issue.
‘model.frame.default()’ allowed ‘data = 1’, leading to involuntary
variable capture (rest of PR#17879).
Fix incorrect calculation in ‘logLik.nls()’ PR#16100, patch from
Sebastian Meyer.
‘phyper(11, 15, 0, 12, log.p=TRUE)’ no longer gives ‘NaN’; reported as PR#17271 by Alexey Stukalov.
Fix incorrect calculation in ‘logLik.nls()’ PR#16100, patch from Sebastian Meyer.
A very old bug could cause a segfault in ‘model.matrix()’ when terms involved logical variables. Part of PR#17879.
‘model.frame.default()’ allowed ‘data = 1’, leading to involuntary variable capture (rest of PR#17879).
‘tar()’ no longer skips non-directory files, thanks to a patch by Sebastian Meyer, fixing the remaining part of PR#16716.
‘all.equal(x,y)’ now “sees” the two different ‘NA’s in factors, thanks to Bill Dunlap and others in PR#17897.
‘R_allocLD()’ has been fixed to return memory aligned for long double
type (PR#16534).
‘R_allocLD()’ has been fixed to return memory aligned for long double type PR#16534.
‘fisher.test()’ no longer segfaults when called again after its internal stack has been exceeded PR#17904.
Accessing a long vector represented by a compact integer sequence no longer segfaults (reported and debugged by Hugh Parsonage).
‘duplicated()’ now works also for strings with multiple encodings inside a single vector PR#17809.
‘configure’ checks for a program ‘pkgconf’ if program ‘pkg-config’ is not found. These are now only looked for on the path (like almost all other programs) so if needed specify a full path to the command in ‘PKG_CONFIG’, for example in file ‘config.site’.
When ‘install.packages(type = "source")’ fails to find a package in a repository it mentions package versions which are excluded by their R version requirement and links to hints on why a package might not be found.
‘isS3stdGeneric(f)’ now detects an S3 generic also when it it is ‘trace()’d, thanks to Gabe Becker's PR#17917.
‘quantile(x, pr)’ works more consistently for ‘pr’ values slightly outside [0,1], thanks to Suharto Anggono's PR#17891.
Further, ‘quantile(x, prN, names=FALSE)’ now works even when ‘prN’ contains ‘NA’s, thanks to Anggono's PR#17892. Ditto for ordered factors or ‘Date’ objects when ‘type = 1’ or ‘3’, thanks to PR#17899.
‘R CMD build’ now omits tarballs and binaries of previous builds from the top-level package directory; PR#17828, patch by Sebastian Meyer.
‘all.equal.POSIXt()’ no longer warns about and subsequently ignores inconsistent ‘"tzone"’ attributes, but describes the difference in its return value (PR#17277). This check can be disabled _via_ the new argument ‘check.tzone = FALSE’; as suggested by Sebastian Meyer.
When ‘install.packages()’ fails to find a package in a source repository it mentions package versions which are excluded by their R version requirement and links to hints on why a package might not be found.
‘capture.output()’ no longer uses NSE to evaluate its arguments. This makes evaluation of functions like ‘parent.frame()’ more consistent, thanks to Lionel Henry's PR#17907.
‘packBits(bits, type="double")’ newly works as inverse of ‘numToBits()’, thanks to Bill Dunlap's proposal in PR#17914.
‘...elt()’ now propagates visibility consistently with ‘..n’, thanks to Lionel Henry's PR#17905.
‘c()’ now removes ‘NULL’ arguments before dispatching to methods, thus simplifying the implementation of ‘c()’ methods, _but_ for back compatibility reasons keeps ‘NULL’ when it is the first argument; from a report and patch proposal by Lionel Henry in PR#17900.
‘as.Date(<char>)’ now also works with an initial ‘""’, thanks to Michael Chirico's PR#17909.
‘R CMD check’ can now scan package functions for bogus ‘return’ statements, which were possibly intended as ‘return()’ calls (wish of PR#17180, patch by Sebastian Meyer). This check can be activated via the new environment variable ‘_R_CHECK_BOGUS_RETURN_’, true for ‘--as-cran’.
‘Vectorize()’'s result function's environment no longer keeps unneeded objects.
Libcurl-based internet access, including ‘curlGetHeaders()’, was not respecting the ‘"timeout"’ option.
‘quantile(x, pr)’ works more consistently for ‘pr’ values slightly outside [0,1], thanks to Suharto Anggono's PR#17891.
Further, ‘quantile(x, prN, names=FALSE)’ now works even when ‘prN’ contains ‘NA’s, thanks to Anggono's PR#17892.
‘c()’ now removes ‘NULL’ arguments before dispatching to methods, thus simplifying the implementation of ‘c()’ methods, thanks to the report and patch by Lionel Henry in PR#17900.
‘quantile(x, pr)’ more consistently works for ‘pr’ values slightly outside [0,1], thanks to Suharto Anggono's PR#17891.
For HTML help (both dynamic and static), Rd file links to help pages in external packages are now treated as references to topics rather than file names, and falls back to a file link only if the topic is not found in the target package. The earlier rule which prioritized file names over topics can be restored by setting the environment variable ‘_R_HELP_LINKS_TO_TOPICS_’ to a false value.
‘path.expand()’ can expand ‘~user’ on most Unix-alikes even when ‘readline’ is not in use. It tries harder to expand ‘~’, for example should environment variable ‘HOME’ be unset.
Fix incorrect calculation in ‘logLik.nls()’ PR#16100, patch from Sebastian Meyer.
‘path.expand()’ can expand ‘~user’ on most Unix-alikes even when ‘readline’ is not in use.
There is a new text file ‘src/gnuwin32/README.compilation’, which outlines how C/Fortran code compilation is organized and documents new features:
• R can be built with Link-Time Optimization with a suitable compiler - doing so with GCC 9.2 showed several inconsistencies which have been corrected.
• There is support for cross-compiling the C and Fortran code in R and standard packages on suitable (Linux) platforms. This is mainly intended to allow developers to test later versions of compilers - for example using GCC 9.2 or 10.x has detected issues that GCC 8.3 in Rtools40 does not.
• There is experimental support for cross-building R packages with C, C++ and/or Fortran code.
‘R_allocLD()’ has been fixed to return memory aligned for long double type (PR#16534).
Fix incorrect calculation in ‘logLik.nls’ PR#16100, patch from Sebastian Meyer.
The horizontal position of leaves in a dendrogram is now correct also with ‘center = FALSE’; PR#14938, patch from Sebastian Meyer.
A very old bug could cause a segfault in ‘model.matrix()’ when terms involved logical variables. Related to PR#17879, but not a complete fix for that issue.
‘model.frame.default()’ allowed ‘data = 1’, leading to involuntary variable capture (rest of PR#17879).
‘model.frame.default’ allowed data=1, leading to involuntary variable capture (rest of PR#17879)
A very old bug could cause a segfault in ‘model.matrix()’ when terms involved logical variables. Related to PR#17879, but not a complete fix for that issue.
Horizontal position of leaves in a dendrogram is now correct also with ‘center = FALSE’; PR#14938, patch from Sebastian Meyer.
Functions ‘URLencode()’ and ‘URLdecode()’ in package ‘utils’ now work on vectors of URLs. Based on patch from Bob Rudis submitted with PR#17873.
Low-level socket read/write operations have been fixed to correctly
signal communication errors. Previously, such errors could lead to a
segfault due to invalid memory access. Reported and debugged by Dmitriy
Selivanov in PR#17850.
Low-level socket read/write operations have been fixed to correctly signal communication errors. Previously, such errors could lead to a segfault due to invalid memory access. Reported and debugged by Dmitriy Selivanov in PR#17850.
The ‘LINPACK’ argument to ‘chol.default()’, ‘chol2inv()’, ‘solve.default()’ and ‘svd()’ has been defunct since R 3.1.0. It was silently ignored up to R 4.0.3 but now gives an error.
New functions ‘numToBits()’ and ‘numToInts()’ extend the ‘raw’ conversion utilities to (double precision) ‘numeric’.
The ‘LINPACK’ argument to ‘chol.default()’, ‘chol2inv()’, ‘solve.default()’ and ‘svd()’ has been defunct since R 3.1.0. Using it now gives a warning which will become an error in R 4.1.0.
‘chisq.test(*, simulate.p.value=TRUE)’ and ‘r2dtable()’ now work correctly for large table entries (in the millions). Reported by Sebastian Meyer and investigated by more helpers in PR#16184.
‘R CMD INSTALL’ and ‘R CMD SHLIB’ make use of their flag ‘--use-LTO’ when the ‘LTO_OPT’ make macro is set in file ‘etc/${R_ARCH}/Makeconf’ or in a personal/site ‘Makevars’ file. (For details see ‘Writing R Extensions’ §4.5.)
This provides a valuable check on code consistency. It does work with GCC 8.3 as in Rtools40, but that does not detect everything the CRAN checks with GCC 10 do.
The ‘LINPACK’ argument to ‘chol.default()’, ‘chol2inv()’, ‘solve.default()’ and ‘svd()’ has been defunct since R 3.1.0. It was silently ignored but now gives an error (and packages were still calling it with ‘LINPACK = TRUE’).
‘checkRdContents()’ is now exported from ‘tools’; it and also ‘checkDocFiles()’ have a new option ‘chkInternal’ allowing to check Rd files marked with keyword ‘"internal"’ as well. The latter can be activated for ‘R CMD check’ via experimental environment variable ‘_R_CHECK_RD_INTERNAL_TOO_’.
‘chisq.test(*, simulate.p.value=TRUE)’ and ‘r2dtable()’ now work correctly for large table entries (in the millions). Reported by Sebastian Meyer and investigated by more helpers in PR#16168.
‘rank(x)’ and hence ‘sort(x)’ now work when ‘x’ is an object (as per ‘is.object(x)’) of type ‘"raw"’ _and_ provides a valid ‘`[`’ method, e.g., for ‘gmp::as.bigz(.)’ numbers.
‘R CMD INSTALL’ and ‘R CMD SHLIB’ make use of their flag ‘--use-LTO’ when the ‘LTO_OPT’ make macro is set in file ‘etc/${R_ARCH}/Makeconf’. (For details see ‘Writing R Extensions’ §4.5.)
This provides a valuable check on code consistency. It does work with GCC 8.3 as in Rtools40, but that does not detect everything the CRAN checks with GCC 10 do.
‘R CMD INSTALL’ and ‘R CMD SHLIB’ make use of the flag ‘--use-LTO’ when
the ‘LTO_OPT’ make macro is set in file ‘etc/${R_ARCH}/Makeconf’ - it
is not by default but a setting in ‘MkRules.local’ will be imported
when R is built.
The graphics engine version, ‘R_GE_version’, has been bumped to 13 and so packages that provide graphics devices should be reinstalled.
Graphics devices can now specify ‘canClip = NA_LOGICAL’, in which case the graphics engine will never perform any clipping of output itself.
The clipping that the graphics engine does perform (for both ‘canClip = TRUE’ and ‘canClip = FALSE’) has been improved to avoid producing unnecessary artifacts in clipped output.
The ‘grid’ package now allows ‘gpar(fill)’ to be a ‘linearGradient()’, a ‘radialGradient()’, or a ‘pattern()’. The ‘viewport(clip)’ can now also be a grob, which defines a clipping path, and there is a new ‘viewport(mask)’ that can also be a grob, which defines a mask.
These new features are only supported (so far) on Cairo graphics devices and the ‘pdf()’ device.
Graphics devices can now specify ‘canClip = NA_LOGICAL’, in which case
the graphics engine will never perform any clipping of output itself.
The clipping that the graphics engine does perform (for both ‘canClip = TRUE’ and ‘canClip = FALSE’) has been improved to avoid producing unnecessary artifacts in clipped output.
The ‘grid’ package now allows ‘gpar(fill)’ to be a ‘linearGradient()’,
a ‘radialGradient()’, or a ‘pattern()’. The ‘viewport(clip)’ can now
also be a grob, which defines a clipping path, and there is a new
‘viewport(mask)’ that can also be a grob, which defines a mask.
These new features are only supported (so far) on Cairo graphics devices and the ‘pdf()’ device.
The graphics engine version, ‘R_GE_version’, has been bumped to 13 and so packages that provide graphics devices should be reinstalled.
‘str(xS4)’ now also shows extraneous attributes of an S4 object ‘xS4’.
‘capabilities()’ gets new entry ‘"Rprof"’ which is ‘TRUE’ when R has been configured with the equivalent of ‘--enable-R-profiling’ (as it is by default): related to Michael Orlitzky's report PR#17836.
‘str(xS4)’ now also shows extraneous attributes of an S4 object ‘xS4’.
The _standalone_ ‘libRmath’ math library and R's C API now provide ‘log1pexp()’ again as documented, and gain ‘log1mexp()’.
Function ‘plclust()’ from the package ‘stats’ and ‘package.dependencies()’, ‘pkgDepends()’, ‘getDepList()’, ‘installFoundDepends()’, and ‘vignetteDepends()’ from package ‘tools’ are defunct.
The ‘R CMD check <pkg>’ gives a longer and more comprehensible message when ‘DESCRIPTION’ misses dependencies, e.g., in ‘Imports:’; thanks to the contributors of PR#17179.
‘update.default()’ now calls the generic ‘update()’ on the formula to work correctly for models with extended formulas; as reported and suggested by Neal Fultz in PR#17865.
‘rank(x)’ and hence ‘sort(x)’ now work when ‘x’ is an object (per ‘is.object(x)’) and of type ‘"raw"’, e.g., for ‘gmp::as.bigz(.)’ numbers.
‘R CMD INSTALL’ and ‘R CMD SHLIB’ make use of the flag ‘--use-LTO’ when the ‘LTO_OPT’ make macro is set in file ‘etc/${R_ARCH}/Makeconf’ - it is not by default but a setting in ‘MkRules.local’ will be imported when R is built.
There is a new text file ‘src/gnuwin32/README.compilation’, which outlines how C/Fortran code compilation is organized and documents new features:
• R can be built with Link-Time Optimization with a suitable compiler - doing so with GCC 9.2 showed several inconsistencies which have been corrected.
• There is support for cross-compiling the C and Fortran code in R and standard packages on suitable (Linux) platforms. This is mainly intended to allow developers to test later versions of compilers - for example using GCC 9.2 has detected issues that GCC 8.3 in Rtools40 does not.
• There is experimental support for cross-building R packages with C, C++ and/or Fortran code.
for GCC >= 8, ‘FC_LEN_T’ is defined in ‘config.h’ and hence character lengths are passed from C to Fortran in _inter alia_ BLAS and LAPACK calls.
There is a new text file ‘src/gnuwin32/README.compilation’, which outlines how C/Fortran code compilation is organized and documents two new features:
• R can be built with Link-Time Optimization with a suitable compiler - doing so with GCC 9.2 showed inconsistencies which have been corrected.
• There is support for cross-compiling the C and Fortran code in R and standard packages on suitable (Linux) platforms. This is mainly intended to allow developers to test later versions of compilers - for example using GCC 9.2.1 has detected issues that GCC 8.3 in Rtools40 does not.
Rudimentary support for vi-style tags in ‘rtags()’ and ‘R CMD rtags’, based on patch from Neal Fultz in PR#17214.