Skip to content

Elaboration on default null object specialization. #4

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Elaboration on default null object specialization. #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,7 +110,7 @@ By default, the `some_dependency` will be assigned a _strict_ null object that i

A direct invocation of the initializer will not leave the `some_dependency` attribute uninitialized as `nil`.

The dependency will be assigned the default null object substitute that is constructed dynamically as a function of the `dependency` macro.
The dependency will be assigned the default null object substitute that is constructed dynamically as a function of the `dependency` macro. The default null object may be specialized by implementing a [concrete substitute](#concrete-substitutes).

The value of `some_dependency` that is needed in live operation (the _operational_ implementation) is provided by the `build` constructor (factory) method.

Expand Down