Optimizer trace: table_scan.rows is traced as integer, change to double

I am looking at 10.6 but earlier versions are likely affected, too.

Looking at outputs like this

              {

                "table": "ix",

                "table_scan": {

                  "rows": 1289434,

                  "cost": 23103

                }

"cost" is always integer?
Debugging the code in add_table_scan_values_to_trace() (one of the TWO places which log "table_scan" objects). I see that the cost is double but is written as integer.

Please make sure it is written as double in BOTH places, starting from the earliest applicable version.