On Sun, Aug 4, 2024 at 8:41 PM Nick Lockheart <li...@ageofdream.com> wrote: > > > > > > But that's not quite what the RFC says: > > > > > I am asking that we discuss and vote on the following question: > > > > > > “Should there be some way for developers to signal to the parser at > > > compile time that all unqualified function names found in a > > > namespace context are global, without a namespace lookup?” > > > > Which implies: > > > > 1. There is _some_ change to syntax. > > 2. All unqualified calls become global. > > I did not intend for all unqualified calls to become global, unless the > new directive is present.
Sorry, my language was not precise enough. Your proposal suggests making unqualified calls global when the directive is present, whereas my proposal suggests keeping local scope as a fallback, hence the two not being compatible. What I'm saying is that: 1. If the vote fails, it might have been because some people don't want opt-in behavior. Niels just voiced this opinion. 2. If the vote is accepted, it would void my suggestion, because it is not compatible with the conditions laid out in your proposal. If this were a straw poll, rather than an RFC vote, it would be clearer that there is no mandatory approach or policy being accepted. A vote with multiple options to pick an approach (opt-in through some directive, hard BC break, flipping lookup order, nothing at all) might be more appropriate. Ilija
