toml11/toml
ToruNiina 3624e4b690 fix: put comment just after non-table values
When non-table value is passed to the `operator<<`, it assumes that the
original C++ code looks like the following.

```cpp
std::cout << "key = " << v << std::endl;
```

In this case, the comment associated to `v` should be put just after
`v`, not before.
```toml
key = # comment <= bad
"value"

key = "value" # comment <= good
```

So, if `v` is not a table it would put comments just after the value.
2019-06-28 17:53:19 +09:00
..
combinator.hpp fix sign-compare warning 2019-06-09 12:00:28 -07:00
comments.hpp feat: add ostream operator to comment containers 2019-06-28 14:57:45 +09:00
datetime.hpp refactor: add explicit type conversion 2019-06-21 00:25:57 +09:00
exception.hpp refactor: make include guard style uniform 2019-03-16 14:19:47 +09:00
from.hpp feat: add from<T> and into<T> 2019-03-16 14:27:05 +09:00
get.hpp Merge branch 'master' into v3 2019-06-19 19:53:08 +09:00
into.hpp feat: add from<T> and into<T> 2019-03-16 14:27:05 +09:00
lexer.hpp fix: disallow invalid escape sequence 2019-03-01 22:13:32 +09:00
literal.hpp refactor: remove needless code snippet 2019-06-22 17:52:01 +09:00
parser.hpp refactor: remove needless inline specifier 2019-06-26 21:34:36 +09:00
region.hpp Merge branch 'v3' of github.com:ToruNiina/toml11 into v3 2019-06-21 14:31:52 +09:00
result.hpp feat: use detail::none_t instead of char 2019-05-31 17:07:52 +09:00
serializer.hpp fix: put comment just after non-table values 2019-06-28 17:53:19 +09:00
source_location.hpp refactor: add explicit type conversion 2019-06-21 00:25:57 +09:00
storage.hpp add simplest copyright notice 2018-12-13 20:44:10 +09:00
string.hpp feat: conversion toml::string <-> string_view 2019-04-22 23:18:05 +09:00
traits.hpp Merge branch 'master' into v3 2019-06-19 19:53:08 +09:00
types.hpp feat: remove unused trait types 2019-06-22 17:35:40 +09:00
utility.hpp Fix Visual Studio 2019 warnings in pedantic compilation mode (/W4 /WX) 2019-05-10 14:58:22 +03:00
value.hpp fix: initialize source_location correctly 2019-06-26 21:35:01 +09:00