Type annotation crashes the compiler

[az5112]

Quick Summary: I create a list with List.map. Annotating the type of the list crashes the compiler.

SSCCE

module Main exposing (..)

import Browser
import Html exposing (..)

type alias Model =
    Int

main =
    Browser.element
        { init = \() -> (50, Cmd.none)
        , view = \model -> div [] []
        , update = \msg model -> (model, Cmd.none)
        , subscriptions = \_ -> Sub.none
        }

asRow attrs children =
    let
        -- compiles fine if the type annotation is removed
        cells : List (Html msg) -- <<<<<<<<<<<< crashes the compiler
        cells = List.map asCell children
    in
    div attrs cells

asCell : Html msg -> Html msg
asCell node =
    div [] [node]

The error is:

Compiling ...elm: You ran into a compiler bug. Here are some details for the developers:

    msg [rank = 2]

Please create an <http://sscce.org/> and then report it
at <https://github.com/elm/compiler/issues>


CallStack (from HasCallStack):
  error, called at compiler/src/Type/Solve.hs:206:15 in main:Type.Solve

-- ERROR -----------------------------------------------------------------------

I ran into something that bypassed the normal error reporting process! I
extracted whatever information I could from the internal error:

>   thread blocked indefinitely in an MVar operation

These errors are usually pretty confusing, so start by asking around on one of
forums listed at https://elm-lang.org/community to see if anyone can get you
unstuck quickly.

-- REQUEST ---------------------------------------------------------------------

If you are feeling up to it, please try to get your code down to the smallest
version that still triggers this message. Ideally in a single Main.elm and
elm.json file.

From there open a NEW issue at https://github.com/elm/compiler/issues with your
reduced example pasted in directly. (Not a link to a repo or gist!) Do not worry
about if someone else saw something similar. More examples is better!

This kind of error is usually tied up in larger architectural choices that are
hard to change, so even when we have a couple good examples, it can take some
time to resolve in a solid way.elm: thread blocked indefinitely in an MVar operation

• Elm: Elm 0.19.1
• Operating System: MacOS

Additional Details

Looks similar to #2295 reported two days ago.

[github-actions]

Thanks for reporting this! To set expectations:

• Issues are reviewed in batches, so it can take some time to get a response.
• Ask questions in a community forum. You will get an answer quicker that way!
• If you experience something similar, open a new issue. We like duplicates.

Finally, please be patient with the core team. They are trying their best with limited resources.