summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authoroctachron <octa@polychoron.fr>2015-12-08 19:14:34 +0100
committeroctachron <octa@polychoron.fr>2016-04-02 02:15:32 +0200
commite3d578863cc7c6ed89ec96805f33be3899abbd1f (patch)
tree9d7b9e6ef32d428b6b602caadbfe6892d9edbbe5
parente9ff94e1dfc7ca8d45366e3b4c0e6d7db586e6a9 (diff)
downloadocaml-user-defined-indexing-operators.tar.gz
Fix GPR#69 changes: bigarray compatibility sectionuser-defined-indexing-operators
-rw-r--r--Changes12
1 files changed, 12 insertions, 0 deletions
diff --git a/Changes b/Changes
index 4b6440668f..01993e116e 100644
--- a/Changes
+++ b/Changes
@@ -6,6 +6,18 @@ OCaml 4.04.0:
Language features:
==================
+- GPR#69: Custom index operators: ( .() ), ( .[] ), ( .{} ) etc.
+ (Florian Angeletti)
+ The syntax "foo.(bar) <- baz" now desugars into "( .()<- ) foo bar baz"; this
+ should allow user to define their own notations by overriding.
+ The bigarray notations ( .{} ), ( .{,} ) etc. are defined in the Bigarray
+ module, which means that the foo.{bar,baz} syntactic sugar should only be
+ available when the Bigarray is opened. To avoid breaking existing program,
+ the compiler emits, for now, a deprecated warning when these Bigarray
+ operators are used implicitly. Opening either the Bigarray.Operators or
+ Bigarray modules fixes this compatibility problem.
+
+
- GPR#301: local exception declarations "let exception ... in"
(Alain Frisch)