id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	os	architecture	failure	difficulty	testcase	blockedby	blocking	related
7052	Numeric types’ Read instances use exponential CPU/memory	andersk		"Computing
  read ""1e99999999"" :: Int      -- returns 0
  read ""1e99999999"" :: Integer  -- returns [REDACTED]
  read ""1e99999999"" :: Float    -- returns Infinity
  read ""1e99999999"" :: Double   -- returns Infinity
takes rather a lot of CPU time and memory, and adding more digits to the exponent makes it take exponentially more.  In some applications, this behavior could be exploitable as a denial of service.

I’m not sure what the right solution is for Integer, but clearly all the other cases should be optimized to produce 0 or Infinity very quickly."	bug	closed	normal	7.6.1	libraries/base	7.4.2	duplicate			Unknown/Multiple	Unknown/Multiple	Runtime performance bug	Unknown				#5688