Calling print on R6 class with no custom print field can have unintended side-effects in the presence of active bindings. Namely, calling print.R6 results in a call to an active binding. Presumably this side effect is due to the following line in print.R6, but I could be wrong:
Calling print on R6 class with no custom print field can have unintended side-effects in the presence of active bindings. Namely, calling print.R6 results in a call to an active binding. Presumably this side effect is due to the following line in print.R6, but I could be wrong:
Here is working example:
Calling print on the above class results in a call to active binding emptydat.netVar. Declaring custom print method resolves the issue.