BREAKING CHANGE: remove NewResolver NewTransport #12
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.
This diff removes the NewResolver and NewTransport constructors, which were just constructing the zero value.
Semantically, I expect a constructor to create a valid value and I was not doing this. So, the simplest diff/fix for that is to just remove the constructors and their implicit promise they are constructing.
Users of
dnscore
will need to update their code accordinggly:replace
NewTransport()
with&Transport{}
;replace
NewResolver()
with&Resolver{}
.