We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update: The issues that were listed here were actually different bugs. The bug below still persists.
> l = list(a = list(b = 1)) $a $a$b [1] 1 > l$a$b[1] NULL >
But it works like this:
(l$a$b)[1]
I therefore believe this is due to the parser (?)
When fixing this, tests should also cover that:
l <- (1, ); environment()$l[[1]]
l <- (1, ); environment()$l[[1]] = 2
The text was updated successfully, but these errors were encountered:
This is not a problem when relying on the [[ operator:
[[
> l[["a"]][["b"]][1] [1] 1
Sorry, something went wrong.
I will try to also fix this in #172
Related to the [[-assignnment, there is also this bug:
> l = list(environment()) [[1]] <environment 0x6000002980d8> > l[[1]] = 100 Error: Invalid target for assignment backtrace: 1: l[[1]] <- 100 => None >
in this case, $-assignment works fine:
$
> l = list(a = environment()) $a <environment 0x6000002980d8> > l$a = 1 $a [1] 1 > l
Successfully merging a pull request may close this issue.
Update: The issues that were listed here were actually different bugs.
The bug below still persists.
But it works like this:
I therefore believe this is due to the parser (?)
When fixing this, tests should also cover that:
l <- (1, ); environment()$l[[1]]
andl <- (1, ); environment()$l[[1]] = 2
workThe text was updated successfully, but these errors were encountered: