This repository was archived by the owner on Mar 22, 2019. It is now read-only.
don't panic when injecting nil #12
Open
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
Author
|
Injecting nil as a named object gives no error so to be honest I don't know the expected behavior in these cases... |
|
I have reviewed the code. That's Ok. |
|
Created this repo https://github.com/imaramos/goject with the purpose of extend this libary due to the lack of maintainance. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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 the error message: "expected unnamed object value to be a pointer to a struct but got type %!s() with value " is slightly better than the current behavior which is to panic when injecting nil.