Implementing copy_sign function for ESQL

[pabloem]

Implementing copy_sign

[nik9000]

@pabloem pabloem force-pushed the pabloem-copy-sign branch 3 times, most recently from 7c63288 to 2f91dad

Once you've opened the PR try not to force push to it. We squash and rebase on merge so the commits don't make it into the main branch. And reviewers can use the commits to follow along. Don't worry about crafting them carefully, but it is useful to have them.

[pabloem]

Once you've opened the PR try not to force push to it. We squash and rebase on merge so the commits don't make it into the main branch. And reviewers can use the commits to follow along. Don't worry about crafting them carefully, but it is useful to have them.

ah yes my bad! I was force-pushing my initial changes (before any review) - I'll avoid it in the future

[nik9000]

ah yes my bad! I was force-pushing my initial changes (before any review) - I'll avoid it in the future

Eh. It's no big deal. Sometimes you have to. But I tend to never force push any PRs so I never have to worry about if someone is looking yet. Just less stuff for me to even remember.

[elasticsearchmachine]

Pinging @elastic/es-analytical-engine (Team:Analytics)

[nik9000]

I withdraw my main question. I requested a few comments and formatting things, but feel free to merge as soon as you think you've done enough there. No need to wait on me unless you think one of my requests is way off base.

[nik9000]

Use {@code Math.copySign(double magnitude, double sign)} for make this render nicely on mouseover and in the actual generated docs. No one reads those. But we do read the mouseovers.