iSynaptic.Commons
iSynaptic.Commons copied to clipboard
CompositeDisposable, Dispose() call order
Just a thought, but when "disposable" objects do have dependencies among each other and were added to CompositeDisposable in their construction order, wouldn't it be better to dispose them in reversed order by default?
Makes sense - I'll make the change. Good catch!