-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
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
implemented .count(), .isEmpty(), .removeAll() #42
Conversation
Hey guys, it's my first PR ever, so please don't destroy it that much 😄 also advice is much appreciated :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the (your very first) PR 🥇
I had a couple of requests. Also, I've changed the target to be the dev branch, where all the feature branches get merged in first, before getting ready for a release. It's because we currently do one more review before the final merge into master. How this affects contributors: when implementing something, start from a dev branch, create a feature branch, make PR from your feature branch into the dev branch. Something like the git-flow described here: https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow
Of course, there's no need for that now that this PR is already open. You can just commit the requested changes in your master
as you've already started and they'll show up in the PR so we'll be able to merge them into dev
.
I have two questions regarding the .remove() method:
|
Thanks for the reminder. We have
What would be an idiomatic way to handle this in Dart?
|
I would've implemented it with type |
I don't know either unfortunately :/ that's why I've asked but I at least could wrap it with a more meaningful exception message than |
In that case, let's change to bool result and return false for this specific exception (not-found). Other exceptions, if any, should still be propagated. |
so are we going with the two methods approach? |
Ok rethought about the approaches and went with two methods 👍 |
This PR addresses Issue #36.