Skip to content

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in 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