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 6805417
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T19:35:02+00:00 2026-05-26T19:35:02+00:00

Is there a good reason why the type of Prelude.read is read :: Read

  • 0

Is there a good reason why the type of Prelude.read is

read :: Read a => String -> a

rather than returning a Maybe value?

read :: Read a => String -> Maybe a

Since the string might fail to be parseable Haskell, wouldn’t the latter be be more natural?

Or even an Either String a, where Left would contain the original string if it didn’t parse, and Right the result if it did?

Edit:

I’m not trying to get others to write a corresponding wrapper for me. Just seeking reassurance that it’s safe to do so.

  • 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-26T19:35:03+00:00Added an answer on May 26, 2026 at 7:35 pm

    Edit: As of GHC 7.6, readMaybe is available in the Text.Read module in the base package, along with readEither: http://hackage.haskell.org/packages/archive/base/latest/doc/html/Text-Read.html#v:readMaybe


    Great question! The type of read itself isn’t changing anytime soon because that would break lots of things. However, there should be a maybeRead function.

    Why isn’t there? The answer is “inertia”. There was a discussion in ’08 which got derailed by a discussion over “fail.”

    The good news is that folks were sufficiently convinced to start moving away from fail in the libraries. The bad news is that the proposal got lost in the shuffle. There should be such a function, although one is easy to write (and there are zillions of very similar versions floating around many codebases).

    See also this discussion.

    Personally, I use the version from the safe package.

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

Sidebar

Related Questions

Is there a particularly good reason to choose to use an elaborated type specifier
Is there a good reason for this? It is a lame question, but I
Is there any good reason to disallow scriptlet or EL expression to be inserted
If so, can the image be animated? Is there a good reason not to
I was wondering if there is a good reason for ScriptReference not to override
Is there a good reason why the check function in the Contol.Concurent.STM library has
Put differently: Is there a good reason to choose a loosely-typed collection over a
We are warned against magic numbers in code with good reason, but is there
Are there any good reasons for why you would include JavaScript like this: <script
Are there any good reasons to modify your project's build output path from its

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.