Skip to content

Conversation

@alandefreitas
Copy link
Member

No description provided.

@cppalliance-bot
Copy link

cppalliance-bot commented Nov 10, 2025

An automated preview of the documentation is available at https://950.url.prtest2.cppalliance.org/index.html

If more commits are pushed to the pull request, the docs will rebuild at the same URL.

2026-01-20 00:04:33 UTC

@cppalliance-bot
Copy link

cppalliance-bot commented Nov 10, 2025

GCOVR code coverage report https://950.url.prtest2.cppalliance.org/gcovr/index.html
LCOV code coverage report https://950.url.prtest2.cppalliance.org/genhtml/index.html
Coverage Diff https://950.url.prtest2.cppalliance.org/gcovr/coverage_diff.txt

Build time: 2026-01-20 00:17:03 UTC

@codecov
Copy link

codecov bot commented Nov 10, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.34%. Comparing base (142fe37) to head (f7903c1).

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop     #950      +/-   ##
===========================================
+ Coverage    99.22%   99.34%   +0.12%     
===========================================
  Files          160      161       +1     
  Lines         8731     8764      +33     
===========================================
+ Hits          8663     8707      +44     
+ Misses          68       57      -11     
Files with missing lines Coverage Δ
include/boost/url/grammar/detail/range_rule.hpp 100.00% <100.00%> (ø)
include/boost/url/grammar/impl/range_rule.hpp 100.00% <100.00%> (+4.52%) ⬆️
include/boost/url/grammar/range_rule.hpp 100.00% <100.00%> (ø)

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 142fe37...f7903c1. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@alandefreitas alandefreitas force-pushed the range-rule branch 4 times, most recently from 4a8bf6b to 86c0d1b Compare January 19, 2026 22:54
@alandefreitas alandefreitas merged commit 176cea8 into boostorg:develop Jan 20, 2026
48 checks passed
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.

Replace grammar::range recycled-strings mechanism

2 participants