Russ Cox 9035f7aea5 runtime: use internal/strconv ...

Runtime doing its own number formatting dates back to
when runtime was the bottom-most Go package.
Those days are long gone. Use internal/strconv to avoid
duplicating code and also to get better floating-point
formatting:

% go1.24.6 run x.go
+1.234568e+004
% go run x.go
12345.678
%

With accurate floating point it becomes necessary to
introduce separate printers for float32 vs float64 and
for complex64 vs complex128. Otherwise float32(93.7)
prints as 93.69999694824219.

Change-Id: I25ae3f09519342dc3d1dcabf4711651423e00128
Reviewed-on: https://go-review.googlesource.com/c/go/+/716002
Reviewed-by: David Chase <drchase@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>

2025-10-29 11:00:23 -07:00

..

array.go

…

chan1.go

…

chan.go

…

complit.go

…

convert.go

…

cplx0.go

…

cplx0.out

runtime: use internal/strconv

2025-10-29 11:00:23 -07:00

cplx1.go

…

cplx2.go

…

cplx3.go

…

cplx4.go

…

cplx5.go

…

divconst.go

test: document ken/*.go

2012-02-24 16:24:24 +11:00

divmod.go

…

embed.go

…

for.go

…

interbasic.go

…

interfun.go

…

intervar.go

…

label.go

…

litfun.go

…

mfunc.go

…

modconst.go

…

ptrfun.go

…

ptrvar.go

…

range.go

…

rob1.go

…

rob2.go

…

robfor.go

…

robfunc.go

…

shift.go

…

simparray.go

…

simpbool.go

…

simpconv.go

…

simpfun.go

…

simpswitch.go

…

simpvar.go

…

slicearray.go

test/ken/slicearray.go: correct type width in comment

2021-12-05 12:50:44 +00:00

sliceslice.go

…

string.go

…

string.out

…

strvar.go

…