Quick Summary: When a function within a let has an incorrect function signature, the following error occurs, but is resolved when the inline function signature is removed.
Dependencies ready!
Compiling ...elm: You ran into a compiler bug. Here are some details for the developers:
attributes [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
module Main exposing
( A
)
type A attributes
= A
{ b : attributes -> ()
}
a getAttribute =
let
b : attributes -> { value : String }
b attributes =
let
_ =
getAttribute attributes
in
()
in
A
{ b = b
}
Quick Summary: When a function within a let has an incorrect function signature, the following error occurs, but is resolved when the inline function signature is removed.
SSCCE