Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Changed EventLoop{Future,Promise}<()> occurances to EventLoop{Future,Promise}<Void> (#211) #219

Merged
merged 1 commit into from
Mar 22, 2018

Conversation

tib
Copy link
Contributor

@tib tib commented Mar 22, 2018

Motivation:

Fix inconsistency of and <()> occurances in the codebase. (fixes #211)

Modifications:

Changed EventLoop{Future,Promise}<()> occurances to EventLoop{Future,Promise}

Result:

Consistent code style for EventLoopPromise and EventLoopFuture.

All tests have been passed.

…Promise}<Void> (#211)

Motivation:

Fix inconsistency of <Void> and <()> occurances in the codebase.

Modifications:

Changed EventLoop{Future,Promise}<()> occurances to EventLoop{Future,Promise}<Void>

Result:

Consistent code style for EventLoopPromise and EventLoopFuture.
@swift-nio-bot
Copy link

Can one of the admins verify this patch?

@normanmaurer
Copy link
Member

@swift-nio-bot test this please

@normanmaurer normanmaurer requested review from weissi and Lukasa March 22, 2018 15:37
@normanmaurer normanmaurer added this to the 1.3.0 milestone Mar 22, 2018
@normanmaurer normanmaurer added the 🔨 semver/patch No public API change. label Mar 22, 2018
@normanmaurer normanmaurer merged commit 1f83a1d into apple:master Mar 22, 2018
@normanmaurer
Copy link
Member

@tib thanks a lot!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
🔨 semver/patch No public API change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

agree on EventLoop{Future,Promise}<Void> vs EventLoop{Future,Promise}<()>
4 participants