It would be nice to be able to prevent the extension of some strategy or rule at finer granularity than library level. For example, a strategy could be marked as having only one definition, or extension could be limited to a single file. In a large codebase this functions as both documentation and protection against accidental extension. The current alternative is using long names and hoping there will be no collision (which, if it happens, may not be immediately clear).

Submitted by Danny Groenewegen on 1 June 2012 at 14:53