Fix method chaining in sys.Http

[bendmorris]

Fixes #6919

Shoutout to HaxeFoundation/haxe-evolution#36 which would be a cleaner fix.

[ncannasse]

I don't understand why we have method chaining here in the first place since we don't use this style at all in order parts of the Haxe standard library.

[bendmorris]

It is convenient, and strictly more useful than returning nothing. There aren't a lot of places in the API that make sense as a fluent interface. Output could be another example (out.writeInt8(1).writeInt8(2).writeString("apple")) but would require a similar generic hack.

[mockey]

I don't understand why we have method chaining here in the first place since we don't use this style at all in order parts of the Haxe standard library.

That's right, it's rather unusual and surely debatable. But it used to work...

[Simn]

I don't understand why we have method chaining here in the first place since we don't use this style at all in order parts of the Haxe standard library.

I agree with that. The chaining probably creeped in at some point and then was just dragged along. I'd be fine with changing this for Haxe 4, especially if there are problems with it now anyway.

[mockey]

@Simn Hey, are you back for good?

[Simn]

#6980