> .Internal(inspect(1:10))
@300e4e8 13 INTSXP g0c0 [NAM(3)] 1 : 10 (compact)
> .Internal(inspect(seq(1,10)))
@3b6e1f8 13 INTSXP g0c4 [] (len=10, tl=0) 1,2,3,4,5,...
> system.time(1:1e7)
user system elapsed
0 0 0
> system.time(seq(1,1e7))
user system elapsed
0.050.0
I don't have an opinion if this requires 3.5.1 to be released soon(er),
but I have ported to R-patched now. The bug existed in R-devel for a
year without being spotted, which is quite a long time - but it may be
these bugs are hard to find before release, because people testing and
using an u
It seems the fix has not been ported to the patched version of R on
Windows yet. I just tested R version 3.5.0 Patched (2018-04-27
r74667).
IMHO this bug is so bad that it is worth a new release R 3.5.1 before
it starts biting more users like this one
https://stackoverflow.com/q/50077412/559676. B
Hi Tomas,
Sorry for the delayed response. I have tested the problem on the latest R-devel
build (2018-04-27 r74651), and it still exists. RGui is always fine with
Chinese characters, but some IDEs rely on the CLI version of R (e.g. Visual
Studio Code with R plugin).
>Your example print("ABC\u
debugonce() sets a different flag (RSTEP), and this is not queried by
isdebugged(), and it is also not unset by undebug().
Is this expected? If yes, is there a way to query and unset the RSTEP flag
from R code?
❯ f <- function() { }
❯ debugonce(f)
❯ isdebugged(f)
[1] FALSE
❯ undebug(f)
Warning m
