Skip to content

docs: cross-link Own.NET P-034 (runtime lifetime guard) from phase-5 - #39

Merged
PhysShell merged 2 commits into
mainfrom
claude/dotnet-lifetime-analyzer-hzor1x
Jul 9, 2026
Merged

PhysShell merged 2 commits into
mainfrom
claude/dotnet-lifetime-analyzer-hzor1x

Conversation

@PhysShell

Copy link
Copy Markdown
Owner

Что и зачем

Короткая врезка в разделе фазы 5 (runtime correlation) docs/own-net-auditor.md:
обсуждали, есть ли смысл в .NET-аналоге C/C++ практики оборачивать malloc/
free параноидальными enterprise-проверками. Как allocator-шим — почти нет
смысла под CLR; как идея — да, и это буквально уже реализовано здесь (фаза 5,
runtime-contract.md, confirmed/static-only/runtime-only) плюс в Own.NET
статически (OWN001/002/003/014). Единственный реально недостающий кусок —
лёгкий, ClrMD-независимый runtime-guard + disposal quarantine для тестов —
задокументирован отдельным предложением в Own.NET, не здесь; врезка даёт на
него ссылку и объясняет, что это дополнение к фазе 5, а не замена.

Ссылка ведёт на Own.NET P-034 (изначально готовилось как P-026, но
консолидационный PR Own.NET#190 разрулил коллизию семи предложений на этот
номер и перенумеровал; врезка здесь сразу указывает на актуальный P-034).

Docs-only, docs/own-net-auditor.md — правки не затрагивают код/пайплайн.

Test plan

  • Docs-only; ссылка резолвится (Own.NET/docs/proposals/P-034-runtime-lifetime-guard.md), код-фенсы и структура документа не нарушены.

Generated by Claude Code

PhysShell added 2 commits July 5, 2026 13:26
…e-5 section

A design discussion asked whether the C/C++ "harden malloc/free"
pattern has a .NET analog. Answer: as an allocator shim, no; as an
idea, it's already OWN001/002/003/014 + phase-5 heap correlation. The
one genuinely missing piece — a lightweight, ClrMD-free runtime guard
usable in ordinary tests — is now tracked in Own.NET's P-026, not
lost in chat history.
@coderabbitai

coderabbitai Bot commented Jul 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@PhysShell, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d85f5300-bbd5-49e1-8dbd-a6373dbf6bae

📥 Commits

Reviewing files that changed from the base of the PR and between c22e889 and 81e7845.

📒 Files selected for processing (1)
  • docs/own-net-auditor.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/dotnet-lifetime-analyzer-hzor1x

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@PhysShell
PhysShell merged commit 98b512d into main Jul 9, 2026
3 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.

1 participant