Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document new features in 4.03 #7092

Closed
vicuna opened this issue Dec 14, 2015 · 9 comments
Closed

Document new features in 4.03 #7092

vicuna opened this issue Dec 14, 2015 · 9 comments
Assignees
Milestone

Comments

@vicuna
Copy link

@vicuna vicuna commented Dec 14, 2015

Original bug ID: 7092
Reporter: @alainfrisch
Assigned to: @alainfrisch
Status: closed (set by @xavierleroy on 2017-09-24T15:32:18Z)
Resolution: fixed
Priority: normal
Severity: major
Target version: 4.03.0+dev / +beta1
Fixed in version: 4.03.0+dev / +beta1
Category: documentation
Monitored by: @gasche @hcarty

Bug description

This ticket is to check that at least new syntactic forms are documented in 4.03 (from the "Language features" section of the Changes file):

=================================================================

DONE:

  • Inlined records

  • "_ t" as a short-hand for "(_, ... _) t".

  • "(type a b)" as syntactic sugar for "(type a) (type b)".

  • Short functor syntax "S -> T".

  • Field punning in object copying expressions "{< x = x; y = y >}".

  • Type annotations on record fields.

  • Type annotations before the "->" in "fun -> ".

  • Hexadecimal notation for fp literals.

  • Unreachable cases ("pat -> .")

  • #5780: Strange type variable names in error messages (GADTs)
    (only made the names more informative)

  • #112: octal escape sequences for char and string literals

  • #234: Allow [] as a user-defined constructor
    #234

  • immediate attribute: commit 461b259

  • #6113: Add descriptions to directives, and display them via #help: commits 213f51a and 58c6347

@vicuna
Copy link
Author

@vicuna vicuna commented Dec 14, 2015

Comment author: @Octachron

Another feature that might be worth documenting is the new naming scheme for GADT-introduced types in error messages, described as

  • #5780: Strange type variable names in error messages (GADTs)
    (only made the names more informative)

in the changelog.

@vicuna
Copy link
Author

@vicuna vicuna commented Dec 23, 2015

Comment author: @Octachron

For ulterior references:

  • "_ t" as a short-hand for "(_, ... _) t": commit a095100

  • "(type a b)" as syntactic sugar for "(type a) (type b)": commit e83d8a6

  • Short functor syntax "S -> T": commit d4bb184

  • Field punning in object copying expressions "{< x = x; y = y >}": commit ec47e31

  • Type annotations on record fields: commit 5af5540.

  • Type annotations before the "->" in "fun -> ": commit c007c77 and b424516

  • Hexadecimal notation for fp literals: commit b2449a3.

The documentation on

  • Unreachable cases ("pat -> .")

is still missing.

@vicuna
Copy link
Author

@vicuna vicuna commented Jan 15, 2016

Comment author: @alainfrisch

29c907d: add description of refutation cases
c7b21e1: nomenclature for existential type names

@vicuna
Copy link
Author

@vicuna vicuna commented Jan 15, 2016

Comment author: @alainfrisch

Or listed items have been documented. There probably remains a lot of missing stuff, so I propose to keep this ticket open as reminder until the release. If someone feels like scanning the Changes file to extract the list of items to remain to be documented, this would be very useful.

@vicuna
Copy link
Author

@vicuna vicuna commented Jan 15, 2016

Comment author: @Octachron

A possible item to document would be the new #help directive

  • #6113: Add descriptions to directives, and display them via #help
    (Nick Giannarakis, Berke Durak, Francis Southern and Gabriel Scherer)

@vicuna
Copy link
Author

@vicuna vicuna commented Jan 29, 2016

Comment author: runhang

need to document this:

GPR234: Allow [] as a user-defined constructor

#234

@vicuna
Copy link
Author

@vicuna vicuna commented Feb 8, 2016

Comment author: @damiendoligez

e92e57d: #112: octal escape sequences for char and string literals

@vicuna
Copy link
Author

@vicuna vicuna commented Feb 8, 2016

Comment author: @damiendoligez

7715890: #234: Allow [] as a user-defined constructor

@vicuna
Copy link
Author

@vicuna vicuna commented Feb 12, 2016

Comment author: @Octachron

Two more items documented:

@vicuna vicuna closed this as completed Sep 24, 2017
@vicuna vicuna added this to the 4.03.0 milestone Mar 14, 2019
@vicuna vicuna added the bug label Mar 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants