| Anonymous | Login | Signup for a new account | 2013-05-25 00:21 CEST | ![]() |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
| 0005728 | OCaml | OCaml general | public | 2012-08-16 09:10 | 2012-11-06 13:41 | ||||||
| Reporter | furuse | ||||||||||
| Assigned To | |||||||||||
| Priority | normal | Severity | feature | Reproducibility | always | ||||||
| Status | acknowledged | Resolution | open | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | 4.00.0 | ||||||||||
| Target Version | Fixed in Version | ||||||||||
| Summary | 0005728: Better handling of unary tuple type | ||||||||||
| Description | Playing with compiler-libs, I found that it is now rather easy to create an unary tuple value Parsetree node and it is typable with a strange unary tuple type. Of course it is the user's responsibility not to create such strange AST nodes, but I think the compiler can provide some help by explicitly rejecting the typing of unary tuples. BTW, the type error message related with this unary tuple type looks very cryptic: Error: This expression has type 'a but an expression was expected of type string Here 'a is not a simple Tvar but something to be printed like Tuple('a), which is not unifiable with string. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
Relationships |
||||||
|
||||||
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2012-08-16 09:10 | furuse | New Issue | |
| 2012-09-06 16:43 | doligez | Target Version | => 4.00.1+dev |
| 2012-09-28 09:50 | doligez | Severity | minor => feature |
| 2012-09-28 09:50 | doligez | Status | new => acknowledged |
| 2012-09-28 09:50 | doligez | Target Version | 4.00.1+dev => |
| 2012-11-06 13:41 | gasche | Relationship added | related to 0005811 |
| Copyright © 2000 - 2011 MantisBT Group |