Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Introducing Timer.record(_ duration:), closes #114 #133
Introducing Timer.record(_ duration:), closes #114 #133
Changes from 1 commit
37ae7aa
e0ce4e8
d0bd9aa
9cccde4
b019460
02fc732
f8316f2
9b835a7
fd5b5d2
84db69d
99ec049
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do the same for earlier versions of Swift? this one is for the availability.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tried that —
#available
doesn't like to be treated as an expression and only works withguard
andif
, seemingly. Didn't try for the language check, though. Let me see if that works.UPD: I think wrapping the check in a closure before feeding it to
XCSkipIf
works. Might look ugly, trying it out now.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
adding an
#else
does not work?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That works! But mixing
#if
and regularif
looks weird to me. Perhaps two separate for#available
and#if swift
are okay?Looks more readable? The closure with nested ifs and explicit returns seems too verbose.
Should I stick with two separate checks?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we will have to
#if swift(>=5.7)
around the entire body of the test as done now since it used types that are not available in previous versions (build will fail) but we can add an#else
to throw XCTSkip thereThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
note tested, but...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright! Pushed up.
UPD wait a sec, broke CI.
XCTSkip
is not available on Swift 5.0 and 5.1 🤦🏼There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay,
I think that'd be good enough, Swift 5.1 is not that common anymore anyway?