It was just since open is a main keyword in the swift programming language we would rather not use it as is.
So in general, any swift keyword should be modified even if the compiler doesn't get complain about it.

I think that is a bit harsh, you may use swift keywords everywhere else in the language if enclosing them in backticks - - so instead of generating a different name, couldn't they be enclosed in instead, then we'll be guaranteed to not break things while still not restricting the names unnecessarily?

From the Swift documentation:

To use a reserved word as an identifier, put a backtick (`) before and after it. For example, class isn’t a valid identifier, but `class` is valid. The backticks aren’t considered part of the identifier; `x` and x have the same meaning.

I mean we can definitely try that as long as the over head of the change isn't big. Because the lib was migrated to use a central namer, and as long as its for variables.

It was just since open is a main keyword in the swift programming language we would rather not use it as is.
So in general, any swift keyword should be modified even if the compiler doesn't get complain about it.

That's my personal opinion, and i usually go for that option when writing code