Skip to content

style(clang-tidy): fix modernize-use-ranges checks #1802

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 4, 2025

Conversation

bavulapati
Copy link
Contributor

No description provided.

Signed-off-by: Balakrishna Avulapati <ba@bavulapati.com>
Signed-off-by: Balakrishna Avulapati <ba@bavulapati.com>
@jviotti
Copy link
Member

jviotti commented Jul 3, 2025

Looks good, but can send a draft PR upgrading Core to this PR commit in https://github.com/sourcemeta/jsonschema and see what CI says? If I recall correctly, I think the JSON Schema CLI build will fail as ranges support is not very widespread yet, but maybe I'm wrong. If the CLI works, we can merge :)

@bavulapati
Copy link
Contributor Author

@jviotti Which standard do we use on jsonschema CLI? Core uses C++20.
And ranges are introduced in C++ 20.

@jviotti
Copy link
Member

jviotti commented Jul 3, 2025

Yes, it's C++20. The problem is that not all compilers support all C++20 features. Some support only a subset. Last time I tried ranges, it was still not supported on Linux I think, as we build the CLI on Ubuntu 22.04 for higher GLIBC support. If you send a PR to the CLI, we can confirm pretty quickly. You can just update the DEPENDENCIES to point core to the SHA of your PR, run ./vendor/vendorpull/pull core and send a draft PR

bavulapati added a commit to bavulapati/jsonschema that referenced this pull request Jul 4, 2025
Refs sourcemeta/core#1802

Signed-off-by: Balakrishna Avulapati <ba@bavulapati.com>
@bavulapati
Copy link
Contributor Author

@jviotti Here we go sourcemeta/jsonschema#391

@jviotti
Copy link
Member

jviotti commented Jul 4, 2025

Oh wonderful. It worked now. Let's do it!

@jviotti jviotti merged commit bfda3a7 into sourcemeta:main Jul 4, 2025
14 checks passed
@jviotti
Copy link
Member

jviotti commented Jul 4, 2025

@bavulapati Feel free to close the other JSON Schema CLI PR if you want. I'll eventually upgrade Core on it when needed (unless you want to point it to a SHA on main and get it merged)

@bavulapati bavulapati deleted the fix-modernize-use-ranges branch July 4, 2025 12:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants