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

expr.{expr} form not documented #5035

Closed
vicuna opened this issue Apr 24, 2010 · 3 comments
Closed

expr.{expr} form not documented #5035

vicuna opened this issue Apr 24, 2010 · 3 comments

Comments

@vicuna
Copy link

vicuna commented Apr 24, 2010

Original bug ID: 5035
Reporter: kaustuv
Status: closed (set by @xavierleroy on 2015-12-11T18:18:30Z)
Resolution: fixed
Priority: normal
Severity: text
Version: 3.11.2
Target version: 4.00.2+dev
Category: documentation
Duplicate of: #3688

Bug description

The manual page for expressions (http://caml.inria.fr/pub/docs/manual-ocaml/expr.html) does not document the forms

| expr.{expr}
| expr.{expr} <- expr

@vicuna
Copy link
Author

vicuna commented Jun 1, 2011

Comment author: @damiendoligez

Should this be documented in chapter 7?

@vicuna
Copy link
Author

vicuna commented Jun 7, 2011

Comment author: lavi

Another sligthly related wish: It would be nice if documentation clearly specify which function is called for which construction (this is the same with expression expr.(expr) and expr.[expr]). So that reuse of those syntax would not be left unspecified.

@vicuna
Copy link
Author

vicuna commented Feb 19, 2013

Comment author: @damiendoligez

Original PR: fixed (commit 13301), including documentation of the functions called for expr.{expr} and expr.{expr}<-expr.

I don't think we want to document the functions called for expr.(expr) and expr.[expr] because:

  1. we don't want to encourage people to redefine them
  2. we want to be able to change them in the future (for example when we implement namespaces)

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

1 participant