This PR makes changes to allow for a flow mapping value to be specified right after the ":" mapping value indicator if its key is JSON-like (surrounded by indicators like {}, [], "" or '') since the YAML specification allows that for JSON compatibility (see here).
With the changes, the following YAML (and minified JSON) is now parsed without any problem.

YAML

{
  "foo":true,
  'bar':false,
  {[1,2,3]:"baz"}:3.14
}

JSON (Minified)

{"foo",true,"bar":false,"baz":null}

Pull Request Checklist

Read the CONTRIBUTING.md file for detailed information.

• Changes are described in the pull request or in a referenced issue.
• The test suite compiles and runs without any error.
• The code coverage on your branch is 100%.
• The documentation is updated if you added/changed a feature.

Please don't

• The C++11 support varies between different compilers and versions. Please note the list of supported compilers. Some compilers like GCC 4.7 (and earlier), Clang 3.3 (and earlier), or Microsoft Visual Studio 13.0 and earlier are known not to work due to missing or incomplete C++11 support. Please refrain from proposing changes that work around these compiler's limitations with #ifdefs or other means.
• Please refrain from proposing changes that would break YAML specifications. If you propose a conformant extension of YAML to be supported by the library, please motivate this extension.
• Please do not open pull requests that address multiple issues.