Bad function signature leads to 'EXPECTING DEFINITION'

[Golden-Phy]

Quick Summary: Missing parenthesis of tuples in the type signature of a function, seemingly lead the parser to assume that something is between the signature and definition, instead of raising a syntax error or type mismatch.

SSCCE

module Main exposing (..)

import Browser
import Html exposing (Html, div, text)

-- MAIN
main =
  Browser.sandbox { init = init, update = update, view = view }

-- UPDATE
update : () -> Model -> Model
update _ model =
  model

-- MODEL
type alias Model = Int

init : Model
init = 3

-- VIEW
view : Model -> Html ()
view model =
    div [] [text (Tuple.first (factorial model))]
    
factorial : Int -> String, Int
factorial i=
  if i <= 1 then ("1", 1) else 
    let 
      val = i * (Tuple.second (factorial (i - 1)))
    in
      (String.fromInt val, val)

• Elm: Playground on https://elm-lang.org/try as of 26/5/2024
• Browser: Mozilla Firefox for Fedora 123.0 (64)
• Operating System: Fedora 39

Additional Details

Compiler output:

EXPECTING DEFINITION
Jump to problem
I just saw the type annotation for `factorial` so I was expecting to see its
definition here:

26| factorial : Int -> String, Int

                             ^
Type annotations always appear directly above the relevant definition, without
anything else in between. (Not even doc comments!)

Here is a valid definition (with a type annotation) for reference:

    greet : String -> String
    greet name =
      "Hello " ++ name ++ "!"

The top line (called a "type annotation") is optional. You can leave it off if
you want. As you get more comfortable with Elm and as your project grows, it
becomes more and more valuable to add them though! They work great as
compiler-verified documentation, and they often improve error messages!

[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.