Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0006432OCamlOCaml generalpublic2014-05-19 08:172014-05-19 14:43
Reporterwhitequark 
Assigned Tolpw25 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusresolvedResolutionduplicate 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0006432: Restrictions on exception match cases are too restrictive
DescriptionI have observed that often, it is convenient to combine a catchall case with an exception case, e.g.:

    match ExtUnix.All.uname () with
    | { ExtUnix.All.Uname.sysname = "Linux" } ->
      List.fold_left Filename.concat [xdg_config_home; app; name]
    | _ | exception (ExtUnix.All.Not_available _) ->
      List.fold_left Filename.concat [home; "." ^ app; name]

However, currently, it's not possible to have a toplevel alternation between an exception case and anything else. It doesn't make sense syntactically, and it's needlessly restrictive.
TagsNo tags attached.
Attached Files

- Relationships
duplicate of 0006422acknowledgeddoligez Support "exception" under or-patterns 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2014-05-19 08:17 whitequark New Issue
2014-05-19 09:25 yallop Relationship added duplicate of 0006422
2014-05-19 14:43 lpw25 Status new => resolved
2014-05-19 14:43 lpw25 Resolution open => duplicate
2014-05-19 14:43 lpw25 Assigned To => lpw25


Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker