We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello!
Were you thinking about splitting up the Map class into traits the way methods are categorized in README? Thank you!
Map
The text was updated successfully, but these errors were encountered:
Yes, traits might be a good idea to spit the code into several files
Sorry, something went wrong.
Proposal for remaining parts.
\ArrayAccess, \Countable, \IteratorAggregate, \JsonSerializable
Dividing the source code like that looks reasonable. Can you create a PR that splits the code like that?
No, I'm sorry. I work with code very slowly 🐌
No branches or pull requests
Hello!
Were you thinking about splitting up the
Map
class into traits the way methods are categorized in README?Thank you!
The text was updated successfully, but these errors were encountered: