Thoughts regarding virtual class and methods for DML class

[nwcm]

Thought I'll raise a discussion to see if this would be something dml-lib would want/allow.

To allow extending DML the class and methods would need to be virtual. This could allow custom implementations overriding some of the default behaviour, in an example case always populating x__c field on sobjects or similar neatly with TaggedDML class or similar.

I don't foresee any issues on the lib side adding this. Obviously, there are considerations for anyone extending the DML class, if done unsafely.

An alternative is enhancing hook or similar to allow pre commit functions to modify record state, but that seems more complicated and risky on the lib side.