I would like to suggest that the extension methods which extend ObservableCollection, could be removed or relocated to a separate namespace. This would allow me to have continuous linq based statements in the same class as BCL System.Linq queries. As it
stands, I'm not sure how to do this. Once I add "using ContinuousLinq", all of my queries go through the Clinq extensions.
Sometimes, I don't want things going through Clinq. One example is when an expression includes a lambda delegate. In this case, Clinq throws an exception indicating that it doesn't support lambdas.
The AsReadOnly extension method could provide the "opt in", allowing me to control which queries should be continuous and which should be standard queries.
If the ObservableCollection extensions were removed, then users would need to add AsReadonly() to a query to get it to use CLINQ. If the extensions were moved to a separate namespace, then the user could still get the "automatic" behavior by including
another using statement like "using ContinuousLinq.Auto" or something like that.
Are there downsides or dangers to such a change? Maybe I'm missing something that resulted in the current design decisions.