From 69678aaa35aa9374672f2c7c9b70c97f9be58aca Mon Sep 17 00:00:00 2001
From: Petri Lehtinen <petri@digip.org>
Date: Tue, 19 May 2015 08:48:52 +0300
Subject: [PATCH] doc: Copying doesn't preserve key insertion order

Fixes #237.
---
 doc/apiref.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/doc/apiref.rst b/doc/apiref.rst
index a330089..7cd2483 100644
--- a/doc/apiref.rst
+++ b/doc/apiref.rst
@@ -1510,6 +1510,10 @@ the same child values in the copied value. Deep copying makes a fresh
 copy of the child values, too. Moreover, all the child values are deep
 copied in a recursive fashion.
 
+Copying objects doesn't preserve the insertion order of keys. Deep
+copying also loses the key insertion order of any objects deeper in
+the hierarchy.
+
 .. function:: json_t *json_copy(json_t *value)
 
    .. refcounting:: new