From @pmichaud

Some Perl 6 module writers have been putting nqp​:: calls into their code, as the setting does. While nqp​:: is not necessarily strictly limited to Rakudo -- other implementations can certainly emulate the nqp​:: space -- we should not allow the use of nqp​:: to become standard practice for Perl 6.

So, this ticket is a placemarker to build in a requirement that any use of nqp​:: calls outside of the CORE setting requires a "use nqp;" declaration to be in scope.

I would not want to see "use nqp;" declaration(s) in the core setting itself (the core setting lexically encompasses user mainline) -- I'd prefer for nqp​:: to be enabled in the setting by some external flag.

Pm

@coke - Status changed from 'new' to 'open'

From @stmuk

This was done in Rakudo 2015.04

On Wed Feb 04 07​:33​:06 2015, pmichaud wrote​:

Some Perl 6 module writers have been putting nqp​:: calls into their
code, as the setting does. While nqp​:: is not necessarily strictly
limited to Rakudo -- other implementations can certainly emulate the
nqp​:: space -- we should not allow the use of nqp​:: to become standard
practice for Perl 6.

So, this ticket is a placemarker to build in a requirement that any
use of nqp​:: calls outside of the CORE setting requires a "use nqp;"
declaration to be in scope.

I would not want to see "use nqp;" declaration(s) in the core setting
itself (the core setting lexically encompasses user mainline) -- I'd
prefer for nqp​:: to be enabled in the setting by some external flag.

Pm

@hoelzro - Status changed from 'open' to 'resolved'