throwDecode doesn't have HasCallStack

[phadej]

though throwM does.

So the backtraces collected by exceptions end somewhere inside aeson library, not including the call-site of throwDecode:

*Data.Aeson> :m +Control.Exception
*Data.Aeson Control.Exception> :set -XOverloadedStrings 
*Data.Aeson Control.Exception> throwIO (AesonException "wrong")
*** Exception: aeson: wrong

HasCallStack backtrace:
  throwIO, called at <interactive>:3:1 in interactive:Ghci1

*Data.Aeson Control.Exception> throwDecode "nll" :: IO Int
*** Exception: aeson: Unexpected "nll", expecting JSON value

HasCallStack backtrace:
  throwIO, called at libraries/exceptions/src/Control/Monad/Catch.hs:343:12 in exceptions-0.10.11-97e4:Control.Monad.Catch
  throwM, called at src/Data/Aeson/Decoding.hs:89:61 in aeson-2.3.1.0-inplace:Data.Aeson.Decoding

[Lysxia]

@phadej in your opinion, does adding HasCallStack to a signature count as a breaking change?

[phadej]

@phadej in your opinion, does adding HasCallStack to a signature count as a breaking change?

No, I cannot think of a way that could break downstream.