Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3600934
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T20:33:28+00:00 2026-05-18T20:33:28+00:00

So using GHCI, these statements are equivalent which makes sense to me because the

  • 0

So using GHCI, these statements are equivalent which makes sense to me because the list expression in end0 is syntactic sugar for the list expression in end1:

let end0 [x,y,z] = z

let end1 (x:y:z:[]) = z

But taking the parens out of the pattern of end1 gives me an “Parse error in pattern” error. So why is that? Do the parens have special meaning in a pattern match or is it a precedence issue like I normally think of when I use parens with operators?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-18T20:33:29+00:00Added an answer on May 18, 2026 at 8:33 pm

    It has to do with precedence.

    A function takes precedence over :, so GHC would infer that you are defining the function for x only. That’s why you have to pack it all inside parens.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

So using GHCI, these statements are equivalent which makes sense to me because the
I'm using a library, which I've loaded into GHCI. From the names of the
I'm using GHCi 7.0.3 with the following program that implements type-level list: {-# LANGUAGE
Using C# and System.Data.SqlClient, is there a way to retrieve a list of parameters
According to a number of tutorials (including Real World Haskell) one can, using ghci
So I'm reading http://learnyouahaskell.com/starting-out as it explains lists, and using ghci on Vista 64.
I'm using GHCi (version 6.12.3) to play a bit with Haskell. I recently read
I'm using Haskell 2010.1.0.0.1 with GHC 6. Typing :t at the GHCi prompt followed
So I'm making a list of prime numbers to help me learn haskell using
I have some code which is designed to replace a value in a list

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.