Andrey Somov

@mshima is your PR complete? I see a number of different branches in your fork.

1) First, let us clarify the problem. YAML 1.1/1.2 specification explicitly ignores any comments. Any attempts to keep the comments will make SnakeYAML non-spec-compliant 2) Feel free to make a...

> What might be easy to do... is have the formatter run a quick check to see if any comments are >present in the file, and if so either: This...

Hi, am evaluating the library I see important deviation from the Erlang OTP where the actor simply dies when a message fails and it is up the its supervisor to...

(Well, I am not sure this issue is a good place to discuss. Mailing list would be a better alternative.) Consider the use case: Actor A send 2 messages to...

Hi Kevin, your message does not answer my question. I will try to ask in a different way. Use case: actors A and B send messages to actor C. 1)...

Dear Kevin, thank you for your time and explanations. I see that the library does not promote the "let it crash" approach. Instead it encourages defensive programming (manual try-catch). It...

@danielthegray SnakeYAML has a property to [prohibit the same keys](https://bitbucket.org/snakeyaml/snakeyaml/issues/395/duplicate-key-diagnostics)

Yaml is not thread-safe means that you cannot call methods of the same instance from different threads. I do not see how it might be connected to `val`

@mmeroberts thank you very much for the contribution. The mentioned TODO was removed as non applicable any longer. For your information. The parsing/dumping comments in SnakeYAML is fully functional.