Skip to content

Unique types for sentinel objects - #11

Closed
RazerM wants to merge 1 commit into
python-hyper:masterfrom
RazerM:sentinel
Closed

RazerM wants to merge 1 commit into
python-hyper:masterfrom
RazerM:sentinel

Conversation

@RazerM

@RazerM RazerM commented Aug 6, 2016

Copy link
Copy Markdown

Proposed solution to #8.

In this implementation, an empty Sentinel class replaces the existing one, which unique sentinel types then inherit from (so that Connection.next_event can still check whether an event is an instance of Sentinel).

A make_sentinel function is added to create the type and return an instance.

@codecov-io

codecov-io commented Aug 6, 2016 •

Copy link
Copy Markdown

Current coverage is 100% (diff: 100%)

Merging #11 into master will not change coverage

@@           master   #11   diff @@
===================================
  Files          20    20          
  Lines         867   868     +1   
  Methods         0     0          
  Messages        0     0          
  Branches      169   169          
===================================
+ Hits          867   868     +1   
  Misses          0     0          
  Partials        0     0          

Powered by Codecov. Last update 0f0c468...5b40710

njsmith added a commit that referenced this pull request Oct 25, 2016
This is a reworked version of @RazerM's work in gh-11.
@njsmith

njsmith commented Oct 25, 2016

Copy link
Copy Markdown
Member

See also #18, which is this PR + a somewhat wacky trick added.

@njsmith

njsmith commented Nov 7, 2016

Copy link
Copy Markdown
Member

#18 is merged, so closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants