| Anonymous | Login | Signup for a new account | 2013-05-22 01:40 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 | ||||||
| 0005802 | OCaml | OCaml typing | public | 2012-10-27 15:10 | 2013-01-03 16:43 | ||||||
| Reporter | turpin | ||||||||||
| Assigned To | |||||||||||
| Priority | low | Severity | trivial | Reproducibility | always | ||||||
| Status | acknowledged | Resolution | open | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | 4.00.1 | ||||||||||
| Target Version | 4.01.0+dev | Fixed in Version | |||||||||
| Summary | 0005802: Avoiding "let" as a value name | ||||||||||
| Description | In Typecore, "let" is used as a value name (to avoid changing side-effects when doing eta-expansion). For the purpose of unparsing typedtrees, "_let" or "let_" would be nicer. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0008683) doligez (manager) 2013-01-03 16:43 |
But using _let or let_ would interfere with legitimate programs that use these identifiers. AFAICT, that's the whole point of using a keyword here. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2012-10-27 15:10 | turpin | New Issue | |
| 2013-01-03 16:43 | doligez | Note Added: 0008683 | |
| 2013-01-03 16:43 | doligez | Status | new => acknowledged |
| 2013-01-03 16:43 | doligez | Target Version | => 4.01.0+dev |
|
Issue History |
| Copyright © 2000 - 2011 MantisBT Group |
 |