about naming conflicts in namespaces

[noraj]

cf. crystal-lang/crystal#13203

Preview: https://deploy-preview-680--crystal-book.netlify.app/syntax_and_semantics/naming_conflicts.html

[netlify]

✅ Deploy Preview for crystal-book ready!

Name	Link
🔨 Latest commit	df0b43d
🔍 Latest deploy log	https://app.netlify.com/sites/crystal-book/deploys/6425ff59163051000845695f
😎 Deploy Preview	https://deploy-preview-680--crystal-book.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[straight-shoota]

Thanks for this contribution.

I think we should put this in a different place. It's not really a specification of a language feature. That would just be the last sentence and that's already covered in https://crystal-lang.org/reference/1.7/syntax_and_semantics/the_program.html#top-level-scope

This piece feels more like a mini howto: If you need to deal with this, you can do that (this = naming conflict, that = top-level namespace reference). Maybe we can put it in the Guides section? But guides are typically larger about more complex topics.
Actually, the scope could be a good format for https://stackoverflow.com/ which we endorse as a knowledge base for these kind of problems.

Anyways, I would suggest to make the example fully self-contained. The reader should not need to know anything outside the presented code.

module Bar
  def self.bar
  end
end

module Foo
  def self.foo
    ::Bar.bar
  end

  module Bar
  end
end

Foo.foo

[noraj]

Maybe a "Common issues" section under https://crystal-lang.org/reference/1.7/guides/index.html?

[beta-ziliani]

I think it's better to have something like this in the tutorial, although at the moment the tutorial itself is rather poor