Thank you for this report.
This sounds a similar issue you encountered to that in https://rdotnet.codeplex.com/discussions/441642. As mentioned in that discussion, this deserves a unit test. If you can provide a small C#/R code illustrating the behavior with/without your workaround, this would be great
This sounds a similar issue you encountered to that in https://rdotnet.codeplex.com/discussions/441642. As mentioned in that discussion, this deserves a unit test. If you can provide a small C#/R code illustrating the behavior with/without your workaround, this would be great