RUMM-669 Xcode 11.3.1 compilation fix

[buranmert]

What and why?

Xcode 11.3.1 doesn't have iOS 13.4 as base SDK
therefore #available(iOS 13.4) closures don't compile

For more: #214

How?

We added compiler version macros as workaround

#if compiler(>=5.2)
  if #available(iOS 13.4, *) { newMethod() }
  else { legacy() }
#else
legacy()
#endif

Note: It's not trivial to run our tests in different Xcode versions with our CI provider

Release info

This PR is branched off from 1.3.0 tag and to be merged into master
We will ship this change as a hotfix once it is merged

Review checklist

• Feature or bugfix MUST have appropriate tests (unit, integration)
• Make sure each commit and the PR mention the Issue number or JIRA reference

[ncreated]

nit: we can keep its original order

Suggested change

	let data = fileHandle.readDataToEndOfFile()
	try? objcExceptionHandler.rethrowToSwift {
	fileHandle.closeFile()
	}
	return data
	defer {
	try? objcExceptionHandler.rethrowToSwift {
	fileHandle.closeFile()
	}
	}
	fileHandle.readDataToEndOfFile()

[buranmert]

previous code was closing fileHandle in defer block, this is the original order as readDataToEndOfFile doesn't throw and closeFile is called after reading

[ncreated]

You're right. I updated my suggestion. Anyway, it does the same as the code in PR 👍.

[buranmert]

yes, it does the same thing, i go with shorter code 🩳

[ncreated]

Why do we need all these changes in swizzling code?

[buranmert]

@ncreated i changed the order of parameters in MethodSwizzler because apparently Xcode 11.3.1 has a problem with parameter ordering. it looks like we need to put the block parameter (instead of default value parameter) at the end

other Xcode versions don't have this issue