This repository was archived by the owner on Nov 27, 2020. It is now read-only.
Unregister initial loader when using ApcClassLoader #570
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fabpot
added a commit
that referenced
this pull request
Jul 10, 2013
This PR was merged into the master branch. Discussion ---------- Unregister initial loader when using ApcClassLoader I think it's quite bad to have twice the same loader registered because for autoloading classes (or class_exists calls) not handled by the main symfony/composer loader, it'll be called twice. Commits ------- 43b3c14 Unregister initial loader when using ApcClassLoader
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think it's quite bad to have twice the same loader registered because for autoloading classes (or class_exists calls) not handled by the main symfony/composer loader, it'll be called twice.