-
Notifications
You must be signed in to change notification settings - Fork 9
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
Create a clean implementation for NOT_A_VALUE #280
Comments
This was referenced Feb 5, 2019
jvdb
added a commit
that referenced
this issue
Feb 7, 2019
jvdb
added a commit
that referenced
this issue
Feb 7, 2019
jvdb
added a commit
that referenced
this issue
Feb 8, 2019
jvdb
added a commit
that referenced
this issue
Feb 10, 2019
jvdb
added a commit
that referenced
this issue
Feb 10, 2019
jvdb
added a commit
that referenced
this issue
Feb 11, 2019
#282 is merged, so issue closed (no autoclose it seems because it was merged through another branch/PR first...) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The work on #279 will lead to a rather simple approach to
NOT_A_VALUE
that is a little error-prone (basically, because it is possible for a user of the library to create a validValue
object that is the same as theNOT_A_VALUE
-constant).A clean approach will be to split
Value
into aValue
interface and aValueImpl
(orBaseValue
,CoreValue
, ...) class. ANotAValue
class can then be created with only aprivate
constructor that is called when instantiating the constant. TheValueImpl
's constructor(s) can then forbid constructing a zero-sizedValue
.The text was updated successfully, but these errors were encountered: