unwrapTryTuple only accepted rvalue tuple types

[folly.git] / folly / docs / Dynamic.md

diff --git a/folly/docs/Dynamic.md b/folly/docs/Dynamic.md
index 7ffb009b2571a09f62e1b6ba7739da3e13cea2da..5cf5ed2cb200a2792f776e8ad7f0a5aeae6e8c60 100644 (file)
--- a/folly/docs/Dynamic.md
+++ b/folly/docs/Dynamic.md
@@ -25,7 +25,7 @@ folly::dynamic;` was used):
     dynamic nul = nullptr;
     dynamic boolean = false;
 
-    // Arrays can be initialized with brackets.
+    // Arrays can be initialized with dynamic::array.
     dynamic array = dynamic::array("array ", "of ", 4, " elements");
     assert(array.size() == 4);
     dynamic emptyArray = dynamic::array;
@@ -120,7 +120,7 @@ which returns an iterator compatible with `items()`:
     // pos->first is "hello"
     // pos->second is "world"
 
-    auto pos = obj.find("no_such_key);
+    auto pos = obj.find("no_such_key");
     // pos == obj.items().end()
 ```
 
@@ -173,19 +173,6 @@ static types, etc).
 ### Some Design Rationale
 ***
 
-**Q. Why is there no default constructor?**
-
-This is a bit of a limitation of `std::initializer_list<>` for
-this use case. The expression `dynamic d = {}` is required by the
-standard to call the default constructor if one exists (the
-reasoning for this makes sense, since `{}` is part of the concept
-of "uniform initialization", and is intended for use with things
-like `std::vector`). It would be surprising if this expression
-didn't leave `d.isArray()` true, but on the other hand it would
-also be surprising if `dynamic d` left `d.isArray()` as true. The
-solution was just to disallow uninitialized dynamics: every
-dynamic must start out being assigned to some value (or nullptr).
-
 **Q. Why doesn't a dynamic string support begin(), end(), and operator[]?**
 
 The value_type of a dynamic iterator is `dynamic`, and `operator[]`