Allow private types in pretty print (#116)

Closes #115

The default print of `"?"` for private implementation classes can be
confusing, especially cases like `[Uri.parse('')]` which pretty prints
as `[?:]`.

- Add more types to print like "primitives" where they already include
  the type name in their default `toString`.
- Remove handling of `null`, it is handled already in the calling
  function.
- Add handling for some core types that are backed by private
  implementation classes.
- Remove the unnecessary try/catch and outdated comments.
3 files changed
tree: c64d3dfeefa344c426116108210858c9fc956380
  1. .gitignore
  2. .test_config
  3. .travis.yml
  4. CHANGELOG.md
  5. LICENSE
  6. README.md
  7. analysis_options.yaml
  8. lib/
  9. pubspec.yaml
  10. test/
README.md

Support for specifying test expectations, such as for unit tests.

The matcher library provides a third-generation assertion mechanism, drawing inspiration from Hamcrest.

For more information, see Unit Testing with Dart.