connection VS mitls-fstar

Trying to build the "old" hs-connection (which is still in my my project's dependency tree) after a cabal update, I now get this : Network/Connection.hs:123:43: error: • Couldn't match expected type ‘crypton-x509-store-1.6.9:Data.X509.CertificateStore.CertificateStore’ with actual type ‘Data.X509.CertificateStore.CertificateStore’ NB: ‘crypton-x509-store-1.6.9:Data.X509.CertificateStore.CertificateStore’ is defined in ‘Data.X509.CertificateStore’ in package ‘crypton-x509-store-1.6.9’ ‘Data.X509.CertificateStore.CertificateStore’ is defined in ‘Data.X509.CertificateStore’ in package ‘x509-store-1.6.9’ • In the ‘sharedCAStore’ field of a record In the ‘clientShared’ field of a record In the expression: (TLS.defaultParamsClient (fst cid) portString) {TLS.clientSupported = def {TLS.supportedCiphers = TLS.ciphersuite_default}, TLS.clientShared = def {TLS.sharedCAStore = globalCertificateStore cg, TLS.sharedValidationCache = validationCache}} | 123 | { TLS.sharedCAStore = globalCertificateStore cg | Error: cabal: Failed to build connection-0.3.1.

So is this library actually going to make an effort about security? E.g. how will it protect against side channel attacks? There's little to no research about whether Haskell is actually suitable for this. All other proper attempts of utilizing functional languages and elaborate type systems for crypto are a bit more complicated and usually transpile to another language, e.g. https://github.com/project-everest/mitls-fstar/issues/124