Skip to content
This repository has been archived by the owner on Feb 4, 2024. It is now read-only.

prevent usage of toString serialization if maxDepth is reached #61

Open
tobiasstamann opened this issue Mar 10, 2017 · 0 comments
Open

Comments

@tobiasstamann
Copy link
Member

Calling toString method on non atomic types can cause serious issues like:

  • breaking the output format
  • trigger endless loops in application code if toString is implemented in a bad way
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant