Fix ios compilation

[tamird]

r? @alexcrichton cc @vhbit

[vhbit]

1. Such a huge whitespace/newline changes should be in a separate PR as they hide the intention and aren't relevant to iOS
2. I wouldn't change dragonfly behavior without knowledge how it works and which constants it uses, i.e. it should remain as it is until maintainer decides to change it.
3. Regarding iOS part everything is OK - this constant exists and while it practically useless, it's easier to enable it than to mess with conditional compilation on dependent modules.

[tamird]

Such a huge whitespace/newline changes should be in a separate PR as they hide the intention and aren't relevant to iOS

Yeah, maybe. It's in a separate commit, we'll see what @alexcrichton says.

I wouldn't change dragonfly behavior without knowledge how it works and which constants it uses, i.e. it should remain as it is until maintainer decides to change it.

I checked the dragonfly source, the constant is correct.

[alexcrichton]

Yeah could the whitespace changes be refactored into a separate PR? Other than that this looks great, thanks!

[tamird]

Done! #23385

[alexcrichton]

@bors: r+

[bors]

@bors r=alexcrichton 04c947c

[bors]

⌛ Testing commit 04c947c with merge 95018ee...

[bors]

☀️ Test successful - auto-linux-32-nopt-t, auto-linux-32-opt, auto-linux-64-nopt-t, auto-linux-64-opt, auto-linux-64-x-android-t, auto-mac-32-opt, auto-mac-64-nopt-t, auto-mac-64-opt, auto-win-32-nopt-t, auto-win-32-opt, auto-win-64-nopt-t, auto-win-64-opt