Are custom file engines in use?

If no custom file engine handlers have been registered, we can avoid
using the Read/Write lock and, most of the time, we also avoid the
creating the handler list at all.

Since the custom handler for QResource's engine has been folded into the
default handler, there should be no other internal use of this API, thus
triggering this optimization by default for all users.

The new flag may also in the future be exported to other modules to
trigger bypassing of file engines completely.

Reviewed-by: Marius Storm-Olsen

0 files changed, 0 insertions, 0 deletions