Draft
Clarify protected behavior for nested namespaces#2554
protected behavior for nested namespaces#2554Conversation
Copilot
AI
changed the title
[WIP] Fix behavior of nested protected namespaces
Clarify Jul 21, 2026
protected behavior for nested namespaces
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
protectedの説明が「フルネームの強制」になっていましたが、ネストした名前空間では実際の挙動とずれていました。protectedが禁止するのは短い名前での参照であり、状況によっては最も近い名前空間名までの修飾で参照できます。説明の修正
LeanByExample/Modifier/Protected.leanの冒頭説明を更新ネストした名前空間の例を追加
protectedな定義が、同じスコープではfooで参照できず、Inner.fooでは参照できる例を追加Outer.Inner.fooが必要になることも併記見出しの表現を調整
SUMMARY.leanの項目名をフルネームを強制するから名前空間名の省略を防ぐに更新例: