Add operator< to json_pointer, to allow use as a map key#3667
Add operator< to json_pointer, to allow use as a map key#3667khiner wants to merge 0 commit intonlohmann:developfrom khiner:develop
operator< to json_pointer, to allow use as a map key#3667Conversation
|
FYI, there's another PR in flight, fixing a regression involving equality comparison (#3664). Seeing that the other operators are missing, I was planning on adding the rest eventually. This is a start. |
|
I am having trouble finding the actual issue behind the failing amalgamation test. As far as I can tell, the indentation style matches the surrounding code exactly. Could someone more familiar with this test please help decipher? 🙏 |
|
|
|
Ah! Sorry I missed that 🤦♂️ |
|
This still looks off. Did you let your editor reformat any of the files? We use Artistic Style which does not create reproducible formatting. I.e., differently formatted input may produce different output. Edit: Specifically, |
|
Hrm, there are no changed files in my |
|
Fixed it for you. https://github.com/khiner/json/pull/1/ |
|
Thanks @falbrechtskirchinger ! I rebased that on my branch. Still not sure why the run output is different between us 🤷♂️ |
|
ayy looks like the other equality operators PR got in, so I'll have to rework this one |
|
We're moving fast right now because we want to get v3.11.2 out the door ASAP. FYI, my Artistic Style version is: Don't know if that might be causing the difference. |
|
Turns out I didn't have I'm opening up a new PR based off current |
Hopefully, the commit description is self-explanatory.
This will require new unit tests, which I can write and add to this PR, but I wanted to get a sanity check that there's not some reason this is a bad idea.
Thank you!