I don't think that is a good idea because to stay consistent multiple versionw of ParseUint, ParseInt, FormatInt and FormatUint would have to be added to the package. Those functions would make the interface of package strconv much larger.
Nobody stops you though to define your private parseFloat32 wrapping ParseFloat. On Wednesday, April 12, 2017 at 7:39:15 PM UTC+2, Andrew Pennebaker wrote: > > Could we separate ParseFloat() into distinct signatures for the > corresponding float widths? Parsing a 32-bit float shouldn't be returned as > a 64-bit float :/ > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
