Antoine Aubry

No worries. I don't want to put pressure on you. Thanks!

This change broke the build - https://ci.appveyor.com/project/aaubry/yamldotnet/builds/44921032 You need to be very careful with line endings because Linux doesn't expect `\r`. Personally I would have preferred not touching the line...

The the PR itself was building correctly - https://ci.appveyor.com/project/aaubry/yamldotnet/builds/44817924. So this is probably a merge error.

The run.sh file hasn't been modified. I guess it's .gitattributes that is causing the problem. I'm not familiar with this file. I always configure git to never modify my line...

This feature has been released in [version 12.0.2](https://github.com/aaubry/YamlDotNet/releases/tag/v12.0.2).

You can extend the various `INodeDeserializer` by registering your own implementation of that interface and add whatever behaviour you need, as shown in that sample. There's no need to change...

This looks good. FYI, I'm currently working on implementing [schemas](https://yaml.org/spec/1.2/spec.html#Schema), based on the 1.2 spec. This may be relevant for this work.

Without further details, it is not clear what would be the correct model to represent your data. One possible approach would be to define a custom type to represent `[0...

You are emitting the comment after the key, that's why it gets in between the key and the `:` indicator. You would need to have a converter to the value...

Thanks for taking the time to look into this. While I agree that the current behavior is buggy, I think that your proposed fix is too specific for floating point...